CVE-2020-16019: Inappropriate implementation in filesystem
Inappropriate implementation in filesystem in Google Chrome on ChromeOS prior to 87.0.4280.66 allowed a remote attacker who had compromised the browser process to bypass noexec restrictions via a malicious file.
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-16018
- CVE-2020-16020
- 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
What is the severity of CVE-2020-16019?
CVE-2020-16019 is classified as a high severity vulnerability due to its potential for exploitation allowing remote attackers to bypass noexec restrictions.
How do I fix CVE-2020-16019?
To fix CVE-2020-16019, upgrade Google Chrome to version 87.0.4280.66 or later.
Which versions of Chrome are affected by CVE-2020-16019?
CVE-2020-16019 affects Google Chrome versions prior to 87.0.4280.66.
Is CVE-2020-16019 present in Chrome OS?
CVE-2020-16019 does not affect Chrome OS, as it is marked as not vulnerable.
Can CVE-2020-16019 allow unauthorized access?
Yes, CVE-2020-16019 potentially allows a remote attacker who has compromised the browser process to execute malicious files.