CVE-2024-22032GO-2024-2932GHSA-Q6C7-56CQ-G2WM
Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec
- 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.14, 2.8.5
- 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: partial
Summary
A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled. When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- github.com/rancher/rancher
From 2.7.0 · fixed in 2.7.14; From 2.8.0 · fixed in 2.8.5
- github.com/rancher/rancherGo
All versions
- github.com/rancher/rancherGo
From 2.7.0 · fixed in 2.7.14
- github.com/rancher/rancherGo
From 2.8.0 · fixed in 2.8.5