Secret disclosure via unsanitized static pod logs
Published Jan 7, 2020 · Updated Aug 5, 2024
Sensitive-data exposure in Red Hat OpenShift library-go as shipped with OpenShift 4.x allows remote authenticated users to read secrets. The static pod logging path writes secret data without sanitization when an operator runs at Debug level or higher. Exploitation requires pod-log access and a privileged user to have enabled the affected log level; the bounded consequence is disclosure of logged secret material.
Summary
What happened
Sensitive-data exposure in Red Hat OpenShift library-go as shipped with OpenShift 4.x allows remote authenticated users to read secrets. The static pod logging path writes secret data without sanitization when an operator runs at Debug level or higher. Exploitation requires pod-log access and a privileged user to have enabled the affected log level; the bounded consequence is disclosure of logged secret material.
The record
- CVE
- CVE-2019-14854
- Published
- Jan 7, 2020
- Updated
- Aug 5, 2024
- Vendor
- Red Hat
- Product
- OpenShift library-go
- Classifications
- CWE-532, CWE-117, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=As shipped with Openshift 4.x
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