First published: Fri Oct 16 2020(Updated: )
Insufficient data validation in cros-disks 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 | <87.0.4280.66 | |
Google Chrome OS | ||
Google Chrome | <87.0.4280.66 | 87.0.4280.66 |
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-16035 is a vulnerability in cros-disks in Google Chrome on ChromeOS prior to version 87.0.4280.66, which allowed a remote attacker to bypass noexec restrictions via a malicious file.
CVE-2020-16035 has a severity level of high.
An attacker can exploit CVE-2020-16035 by compromising the browser process and bypassing noexec restrictions through a malicious file.
Google Chrome versions prior to 87.0.4280.66 are affected by CVE-2020-16035.
To fix CVE-2020-16035, update Google Chrome to version 87.0.4280.66 or later.