Rancher Remote Code Execution via Cluster/Node Drivers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.16, 2.8.9, 2.9.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A vulnerability has been identified within Rancher where a cluster or node driver can be used to escape the chroot jail and gain root access to the Rancher container itself. In production environments, further privilege escalation is possible based on living off the land within the Rancher container itself. For the test and development environments, based on a –privileged Docker container, it is possible to escape the Docker container and gain execution access on the host system. This issue affects rancher: from 2.7.0 before 2.7.16, from 2.8.0 before 2.8.9, from 2.9.0 before 2.9.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- github.com/rancher/rancher
From 2.7.0 · fixed in 2.7.16; From 2.8.0 · fixed in 2.8.9; From 2.9.0 · fixed in 2.9.3
- github.com/rancher/rancherGo
All versions
- github.com/rancher/rancherGo
From 2.7.0 · fixed in 2.7.16
- github.com/rancher/rancherGo
From 2.8.0 · fixed in 2.8.9
- github.com/rancher/rancherGo
From 2.9.0 · fixed in 2.9.3