# CVE-2024-9779: Open-cluster-management-io/ocm: cluster-manager permissions may allow a worker node to obtain service account tokens > An attacker controlling a worker node can steal cluster-manager service account tokens to gain full cluster control. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Dec 2024 - **Updated:** 25 Feb 2026 - **Also known as:** GHSA-jhh6-6fhp-q2xp, GO-2024-3343 ## What is CVE-2024-9779? CVE-2024-9779 is a high-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in Open Cluster Management (OCM) when a user has access to the worker nodes which contain the cluster-manager or klusterlet deployments. The cluster-manager deployment uses a service account with the same name "cluster-manager" which is bound to a ClusterRole also named "cluster-manager", which includes the permission to create Pod resources. If this deployment runs a pod on an attacker-controlled node, the attacker can obtain the cluster-manager's token and steal any service account token by creating and mounting the target service account to control the whole cluster. Weakness: CWE-266 (Incorrect Privilege Assignment) ## Which versions are affected by CVE-2024-9779? 3 open source packages ship an affected version, including open-cluster-management.io/ocm. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `open-cluster-management.io/ocm` | Go | All versions | 0.13.0 | | `open-cluster-management.io/ocm` | Go | All versions | 0.13.0 | | `open-cluster-management.io/ocm` | Go | All versions | 0.13.0 | ## How do I fix CVE-2024-9779? Upgrade open-cluster-management.io/ocm to 0.13.0 or later. ## Is CVE-2024-9779 being exploited? There is no known exploitation of CVE-2024-9779 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-9779 and fix it if it is affected. What it is: CVE-2024-9779 is a high-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-9779 in the wild and no public exploit code. Affected packages and fixed versions: - open-cluster-management.io/ocm (Go): affected all versions; fixed in 0.13.0 - open-cluster-management.io/ocm (Go): affected all versions; fixed in 0.13.0 - open-cluster-management.io/ocm (Go): affected all versions; fixed in 0.13.0 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-9779/ (Markdown: https://insights.sbomify.com/CVE-2024-9779/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9779 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9779 - OSV: https://osv.dev/vulnerability/CVE-2024-9779 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-9779/ Summaries are generated and may contain mistakes; the official description above is the record.