TLS private-key disclosure via readable ConfigMap
Published Sep 1, 2022 · Updated Aug 3, 2024
Information exposure in Red Hat OpenShift Container Platform 4.9 and later allows remote authenticated users to read a cluster TLS private key. The authentication-operator incorrectly stores the external cluster certificate's private key in oauth-serving-cert ConfigMaps where authenticated users and service accounts can read it. Cluster credentials are sufficient to obtain the key and compromise the confidentiality of web traffic protected by the certificate.
Summary
What happened
Information exposure in Red Hat OpenShift Container Platform 4.9 and later allows remote authenticated users to read a cluster TLS private key. The authentication-operator incorrectly stores the external cluster certificate's private key in oauth-serving-cert ConfigMaps where authenticated users and service accounts can read it. Cluster credentials are sufficient to obtain the key and compromise the confidentiality of web traffic protected by the certificate.
The record
- CVE
- CVE-2022-2403
- Published
- Sep 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-497, CWE-668, T1552.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Openshift 4.9 onwards
What conditions does exploitation require?
What is affected?
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