CVE-2023-32191GO-2024-2930GHSA-6GR4-52W6-VMQX
rke's credentials are stored in the RKE1 Cluster state ConfigMap
- 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 1.4.19, 1.5.10
- 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
When RKE provisions a cluster, it stores the cluster state in a configmap called `full-cluster-state` inside the `kube-system` namespace of the cluster itself. The information available in there allows non-admin users to escalate to admin.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- github.com/rancher/rke
From 1.4.18 · fixed in 1.4.19; From 1.5.9 · fixed in 1.5.10
- github.com/rancher/rkeGo
From 1.4.18 · fixed in 1.4.19; From 1.5.9 · fixed in 1.5.10
- github.com/rancher/rkeGo
From 1.4.18 · fixed in 1.4.19
- github.com/rancher/rkeGo
From 1.5.9 · fixed in 1.5.10