First published: Fri Oct 16 2020(Updated: )
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: chrome-cve-admin@google.com Rory McNamara
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome (Trace Event) | <87.0.4280.66 | 87.0.4280.66 |
Google Chrome (Trace Event) | <87.0.4280.66 | |
Chrome OS |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-16019 is classified as a high severity vulnerability due to its potential for exploitation allowing remote attackers to bypass noexec restrictions.
To fix CVE-2020-16019, upgrade Google Chrome to version 87.0.4280.66 or later.
CVE-2020-16019 affects Google Chrome versions prior to 87.0.4280.66.
CVE-2020-16019 does not affect Chrome OS, as it is marked as not vulnerable.
Yes, CVE-2020-16019 potentially allows a remote attacker who has compromised the browser process to execute malicious files.