Storage credential disclosure via unredacted operator logs
Published Apr 22, 2020 · Updated Aug 4, 2024
Sensitive-data exposure in OpenShift Cluster Image Registry Operator 4.1 and later allows attackers with log access to obtain storage credentials. The operator writes cloud-storage credentials used by the registry into diagnostic logs without redacting the secret values. Exploitation requires access to those logs; the credentials grant read and write access to backing storage and permit changes to tag-referenced images.
Summary
What happened
Sensitive-data exposure in OpenShift Cluster Image Registry Operator 4.1 and later allows attackers with log access to obtain storage credentials. The operator writes cloud-storage credentials used by the registry into diagnostic logs without redacting the secret values. Exploitation requires access to those logs; the credentials grant read and write access to backing storage and permit changes to tag-referenced images.
The record
- CVE
- CVE-2020-10712
- Published
- Apr 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift Cluster Image Registry Operator
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=all ose-cluster-image-registry-operator-container 4.1 versions and later
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