Access-control bypass via malicious cryptohome file
Published Jan 8, 2021 · Updated Aug 4, 2024
Access-control bypass in Google Chrome before 87.0.4280.66 on ChromeOS allows remote attackers to evade discretionary file controls. The cryptohome component mishandles a malicious file, but Google has not publicly disclosed the specific code path or incorrect operation. Exploitation requires prior compromise of the browser process and user interaction; the reported consequence is limited to bypassing discretionary access control.
Summary
What happened
Access-control bypass in Google Chrome before 87.0.4280.66 on ChromeOS allows remote attackers to evade discretionary file controls. The cryptohome component mishandles a malicious file, but Google has not publicly disclosed the specific code path or incorrect operation. Exploitation requires prior compromise of the browser process and user interaction; the reported consequence is limited to bypassing discretionary access control.
The record
- CVE
- CVE-2020-16020
- Published
- Jan 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 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=unspecified <87.0.4280.66
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
No sourced classifications are available.
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