Account impersonation via panic-log OAuth token disclosure
Published Jun 12, 2020 · Updated Aug 4, 2024
Credential disclosure in Red Hat OpenShift API Server allows remote authenticated users to obtain OAuth tokens from panic logs. The panic-recovery path writes OAuthToken identifiers containing usable token values to API server logs instead of nonsecret hashes. Exploitation requires the ability to trigger an API server error and read control-plane logs; a recovered token grants its holder that token's API access.
Summary
What happened
Credential disclosure in Red Hat OpenShift API Server allows remote authenticated users to obtain OAuth tokens from panic logs. The panic-recovery path writes OAuthToken identifiers containing usable token values to API server logs instead of nonsecret hashes. Exploitation requires the ability to trigger an API server error and read control-plane logs; a recovered token grants its holder that token's API access.
The record
- CVE
- CVE-2020-10752
- Published
- Jun 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift API Server
- Classifications
- CWE-532, CWE-522, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 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 versions
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