CVE-2020-16020: Inappropriate implementation in cryptohome
Published Oct 16, 2020
·Updated
Inappropriate implementation in cryptohome in Google Chrome on ChromeOS prior to 87.0.4280.66 allowed a remote attacker who had compromised the browser process to bypass discretionary access control via a malicious file.
Credit
Rory McNamara
Affected Software
4 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
Google Chrome<87.0.4280.66
87.0.4280.66
Google Chrome<87.0.4280.66
Google Chrome OS
Event History
Oct 16, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:51 PM
Data Sourced
via MITRE·05:51 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-16018
- CVE-2020-16019
- CVE-2020-16021
- CVE-2020-16022
- CVE-2020-16015
- CVE-2020-16014
- CVE-2020-16023
- CVE-2020-16024
- CVE-2020-16025
- CVE-2020-16045
- CVE-2020-16026
- CVE-2020-16027
- CVE-2020-16028
- CVE-2020-16029
- CVE-2020-16030
- CVE-2019-8075
- CVE-2020-16031
- CVE-2020-16032
- CVE-2020-16033
- CVE-2020-16034
- CVE-2020-16035
- CVE-2020-16012
- CVE-2020-16036
Frequently Asked Questions
1
What is the severity of CVE-2020-16020?
CVE-2020-16020 has been classified as a high severity vulnerability that allows a remote attacker to bypass access controls.
2
How do I fix CVE-2020-16020?
To fix CVE-2020-16020, update Google Chrome to version 87.0.4280.66 or later.
3
What versions of Chrome are affected by CVE-2020-16020?
CVE-2020-16020 affects all versions of Google Chrome prior to version 87.0.4280.66.
4
Can CVE-2020-16020 be exploited remotely?
Yes, CVE-2020-16020 can be exploited remotely by a compromised browser process.
5
Is Chrome OS affected by CVE-2020-16020?
No, Chrome OS is not affected by CVE-2020-16020.