CVE-2024-22031GHSA-8H6M-WV39-239MGO-2025-3647
Rancher users who can create Projects can gain access to arbitrary projects
- 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.9.9, 2.10.5, 2.11.1
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A vulnerability has been identified within Rancher where a user with the ability to create a project, on a certain cluster, can create a project with the same name as an existing project in a different cluster. This results in the user gaining access to the other project in the different cluster, resulting in a privilege escalation. This happens because the namespace used on the local cluster to store related resources (PRTBs and secrets) is the name of the project.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- github.com/rancher/rancher
From 2.8.0 · fixed in 2.9.9; From 2.10.0 · fixed in 2.10.5; From 2.11.0 · fixed in 2.11.1
- github.com/rancher/rancherGo
From 2.8.0 · fixed in 2.9.9
- github.com/rancher/rancherGo
From 2.10.0 · fixed in 2.10.5
- github.com/rancher/rancherGo
From 2.11.0 · fixed in 2.11.1
- github.com/rancher/rancherGo
All versions