Azure service-account takeover via pod environment secret
Published Apr 30, 2024 · Updated Feb 25, 2026
Information disclosure in Red Hat OpenShift Container Platform 4.14 and 4.15 allows remote authenticated users to obtain an Azure client secret. The registry operator places AZURE_CLIENT_SECRET directly in its pod definition as an environment variable instead of using a protected secret reference. Exploitation is limited to Azure clusters and requires permission to read pod information in openshift-image-registry; the credential grants the operator's Azure service-account privileges.
Summary
What happened
Information disclosure in Red Hat OpenShift Container Platform 4.14 and 4.15 allows remote authenticated users to obtain an Azure client secret. The registry operator places AZURE_CLIENT_SECRET directly in its pod definition as an environment variable instead of using a protected secret reference. Exploitation is limited to Azure clusters and requires permission to read pod information in openshift-image-registry; the credential grants the operator's Azure service-account privileges.
The record
- CVE
- CVE-2024-4369
- Published
- Apr 30, 2024
- Updated
- Feb 25, 2026
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform 4.14
- Classifications
- CWE-526, T1552.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 30, 2024CVE publishedPublication date reported by the CVE source.
- Feb 25, 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.
Weakness, pattern, technique
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