cbcvebase.
CVE-2024-45496
published 2024-09-17

CVE-2024-45496: 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…

PriorityP267critical9.9CVSS 3.1
AVNACLPRLUINSCCHIHAL
EPSS
0.89%
55.0th percentile
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.

Affected

1 ranges
VendorProductVersion rangeFixed in
github.comopenshift_openshift-controller-manager>= 0 < 0.0.0-alpha.0.0.202409110.0.0-alpha.0.0.20240911

Detection & IOCsextracted from sources · hover to see the quote

path.gitconfig
processgit-clone
  • ·The 'Custom' build strategy is out of scope for this CVE — it already grants developers permission to run arbitrary commands in a privileged container by design, is disabled by default, and is documented as only for highly trusted users (e.g., cluster admins).
  • ·MicroShift is NOT affected — it does not include the OpenShift API involved in this vulnerability.
  • ·The Builds for Red Hat OpenShift Operator (Shipwright-based) is NOT affected.
  • ·An incomplete fix was identified: even after the CVE-2024-45496 patch, the buildconfigs/instantiate API still lacks a semantic deny-list for dangerous environment variable names, meaning env var injection into privileged docker-build containers remains possible (tracked as CVE-2026-7309). Practical impact is limited to non-standard minimal role configurations since the edit role already grants Secret read access.
  • ·The env var name validation post-fix only applies a format regex with no semantic deny-list for dangerous names, leaving a residual bypass path.

CVSS provenance

nvdv3.19.9CRITICALCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
vendor_redhat9.9CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.