Node compromise via privileged git-clone container
Published Sep 16, 2024 · Updated Aug 11, 2026
Improper privilege management in Red Hat OpenShift 4.12 through 4.18 allows remote authenticated users to execute code on worker nodes. The build controller applies the build strategy's privileged security context to the git-clone init container, which executes commands supplied through a crafted .gitconfig file. Developer-level build access is required; successful exploitation grants unrestricted access to the Linux worker node hosting the build pod.
Summary
What happened
Improper privilege management in Red Hat OpenShift 4.12 through 4.18 allows remote authenticated users to execute code on worker nodes. The build controller applies the build strategy's privileged security context to the git-clone init container, which executes commands supplied through a crafted .gitconfig file. Developer-level build access is required; successful exploitation grants unrestricted access to the Linux worker node hosting the build pod.
The record
- CVE
- CVE-2024-45496
- Published
- Sep 16, 2024
- Updated
- Aug 11, 2026
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform 4.14
- Classifications
- CWE-269, T1611
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo