Rancher Remote Code Execution via Cluster/Node Drivers
SUSE rancher
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/rancher Go |
|
|
SUSE rancher
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/rancher Go |
|
|
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.
From the CVE record · suse
A cluster or node driver can be used to escape its chroot jail and gain root access to the Rancher container. Further privilege escalation may be possible in production; in test or development environments using a privileged Docker container, an attacker can escape the container and execute on the host. The input does not specify authentication or user-interaction requirements.
Operators running Rancher 2.7.0–2.7.15, 2.8.0–2.8.8, or 2.9.0–2.9.2 should check their deployments.