Access-token theft via browser local storage
Published May 27, 2021 · Updated Aug 4, 2024
Information disclosure in Red Hat OpenShift Web Console 3.11 allows attackers to steal access tokens from browser local storage. The console persists the bearer token as LocalStorageUserStore.token, allowing scripts in the console origin to read it after login. Exploitation requires physical browser access or script execution through an XSS flaw, after which the token grants the victim's OpenShift privileges.
Summary
What happened
Information disclosure in Red Hat OpenShift Web Console 3.11 allows attackers to steal access tokens from browser local storage. The console persists the bearer token as LocalStorageUserStore.token, allowing scripts in the console origin to read it after login. Exploitation requires physical browser access or script execution through an XSS flaw, after which the token grants the victim's OpenShift privileges.
The record
- CVE
- CVE-2020-1761
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift Web Console
- Classifications
- CWE-358, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2021CVE 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=openshift/console-4
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