# CVE-2023-32191: rke's credentials are stored in the RKE1 Cluster state ConfigMap

> Attackers with read access to the kube-system namespace can retrieve admin credentials from the cluster state ConfigMap, enabling privilege escalation.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2024
- **Updated:** 16 Oct 2024
- **Also known as:** GHSA-6gr4-52w6-vmqx, GO-2024-2930

## What is CVE-2023-32191?

CVE-2023-32191 is a critical vulnerability in SUSE rke, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2023-32191?

5 open source packages ship an affected version, including github.com/rancher/rke.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rke` | Go | From 1.4.18 | 1.4.19, 1.5.10 |
| `github.com/rancher/rke` | Go | From 1.4.18 | 1.4.19 |
| `github.com/rancher/rke` | Go | From 1.4.18 | 1.4.19 |
| `github.com/rancher/rke` | Go | From 1.5.9 | 1.5.10 |
| `github.com/rancher/rke` | Go | From 1.5.9 | 1.5.10 |

## How do I fix CVE-2023-32191?

Upgrade github.com/rancher/rke to a fixed version for your release line: 1.4.19 or 1.5.10.

## Is CVE-2023-32191 being exploited?

There is no known exploitation of CVE-2023-32191 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32191 and fix it if it is affected.

What it is: CVE-2023-32191 is a critical vulnerability in SUSE rke, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32191 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rke (Go): affected from 1.4.18; fixed in 1.4.19, 1.5.10
- github.com/rancher/rke (Go): affected from 1.4.18; fixed in 1.4.19
- github.com/rancher/rke (Go): affected from 1.4.18; fixed in 1.4.19
- github.com/rancher/rke (Go): affected from 1.5.9; fixed in 1.5.10
- github.com/rancher/rke (Go): affected from 1.5.9; fixed in 1.5.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-32191/ (Markdown: https://insights.sbomify.com/CVE-2023-32191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32191
- OSV: https://osv.dev/vulnerability/CVE-2023-32191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-32191/
Summaries are generated and may contain mistakes; the official description above is the record.