# CVE-2024-22032: Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec

> Attackers with cluster access can view plaintext Kubernetes API secret values due to improper handling of encryption configuration during reconciliation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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-q6c7-56cq-g2wm, GO-2024-2932

## What is CVE-2024-22032?

CVE-2024-22032 is a high-severity vulnerability in SUSE rancher, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-22032?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rancher` | Go | All versions | None |
| `github.com/rancher/rancher` | Go | From 2.7.0 | 2.7.14 |
| `github.com/rancher/rancher` | Go | From 2.7.0 | 2.7.14 |
| `github.com/rancher/rancher` | Go | From 2.8.0 | 2.8.5 |
| `github.com/rancher/rancher` | Go | From 2.8.0 | 2.8.5 |

## How do I fix CVE-2024-22032?

Upgrade github.com/rancher/rancher to a fixed version for your release line: 2.7.14 or 2.8.5.

## Is CVE-2024-22032 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22032 and fix it if it is affected.

What it is: CVE-2024-22032 is a high-severity vulnerability in SUSE rancher, 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-2024-22032 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rancher (Go): affected all versions; no fix listed
- github.com/rancher/rancher (Go): affected from 2.7.0; fixed in 2.7.14
- github.com/rancher/rancher (Go): affected from 2.7.0; fixed in 2.7.14
- github.com/rancher/rancher (Go): affected from 2.8.0; fixed in 2.8.5
- github.com/rancher/rancher (Go): affected from 2.8.0; fixed in 2.8.5

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-2024-22032/ (Markdown: https://insights.sbomify.com/CVE-2024-22032/index.md)
```

## Sources

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

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