CVE-2024-45496: openshift-container-platform · Improper Privilege Management
Affects openshift-container-platformSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Red Hatredhat/openshift-container-platformpkg:rpm/redhat/openshift-container-platformOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Red Hat has released fixed container images and packages for OpenShift Container Platform versions 4.15.33 and 4.17.0 that address this vulnerability. Users should upgrade their OpenShift clusters to these or later versions as soon as they become available in their release channels. The vendor manages remediation for these releases, and detailed upgrade instructions are provided in the Red Hat advisories and OpenShift documentation. No alternative mitigations or workarounds are indicated in the vendor advisory.
Description
A flaw was found in OpenShift. This issue occurs due to the misuse of elevated privileges in the OpenShift Container Platform's build process. During the build initialization step, the git-clone container is run with a privileged security context, allowing unrestricted access to the node. An attacker with developer-level access can provide a crafted .gitconfig file containing commands executed during the cloning process, leading to arbitrary command execution on the worker node. An attacker running code in a privileged container could escalate their permissions on the node running the container.
References
- access.redhat.com/errata/RHSA-2024:3718 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6685 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6687 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6689 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6691 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6705 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2024-45496 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2308661 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:6122 (opens in a new tab)