# CVE-2024-25133: Openshift-dedicated: hive: rce through aws/kubernetes client configuration leads to privilege escalation

> A developer on a Hive-enabled OpenShift Dedicated cluster can escalate to cluster-admin by executing arbitrary commands via client configuration flaws.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 31 Dec 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-wgqq-9qh8-wvqv, GO-2024-3360

## What is CVE-2024-25133?

CVE-2024-25133 is a high-severity vulnerability in github.com/openshift/hive, published on 31 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Hive ClusterDeployments resource in OpenShift Dedicated. In certain conditions, this issue may allow a developer account on a Hive-enabled cluster to obtain cluster-admin privileges by executing arbitrary commands on the hive/hive-controllers pod.

Weakness: CWE-284 (Improper Access Control)

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

3 open source packages ship an affected version, including github.com/openshift/hive.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openshift/hive` | Go | All versions | None |
| `github.com/openshift/hive` | Go | All versions to 1.1.16 | None |
| `github.com/openshift/hive` | Go | All versions to 1.1.16 | None |

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

Apply the vendor's patch.

## Is CVE-2024-25133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25133 is a high-severity vulnerability in github.com/openshift/hive, published on 31 Dec 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-25133 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openshift/hive (Go): affected all versions; no fix listed
- github.com/openshift/hive (Go): affected all versions up to 1.1.16; no fix listed
- github.com/openshift/hive (Go): affected all versions up to 1.1.16; no fix listed

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

## Sources

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

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