CVE-2020-16019

Description

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.

8.8

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.22%

Vendor Advisory googleblog.com Vendor Advisory crbug.com

Affected: Google Chrome

References

Link	Tags
https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_17.html	release notes vendor advisory
https://crbug.com/1139408	permissions required vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-16019?: CVE-2020-16019 has been scored as a high severity vulnerability.
How to fix CVE-2020-16019?: To fix CVE-2020-16019, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-16019 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-16019 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-16019?: CVE-2020-16019 affects Google Chrome.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.