User impersonation via cleartext OAuth token names
Published May 12, 2020 · Updated Aug 4, 2024
Cleartext token storage in Red Hat OpenShift API Server allows attackers with backup access to impersonate recently active users. The OAuth server stores raw OAuthAccessToken and OAuthAuthorizeToken values as API object names, leaving them outside value-only etcd encryption. The flaw requires encryption at rest to be enabled and access to a backup; exposed tokens remain usable for up to 24 hours.
Summary
What happened
Cleartext token storage in Red Hat OpenShift API Server allows attackers with backup access to impersonate recently active users. The OAuth server stores raw OAuthAccessToken and OAuthAuthorizeToken values as API object names, leaving them outside value-only etcd encryption. The flaw requires encryption at rest to be enabled and access to a backup; exposed tokens remain usable for up to 24 hours.
The record
- CVE
- CVE-2020-10706
- Published
- May 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift API Server
- Classifications
- CWE-312, T1550.001
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- May 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=n/a
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