First published: Fri Aug 14 2020(Updated: )
Insufficient policy enforcement in developer tools in Google Chrome prior to 87.0.4280.66 allowed an attacker who convinced a user to install a malicious extension to obtain potentially sensitive information from the user's disk via a crafted Chrome Extension.
Credit: chrome-cve-admin@google.com David Erceg
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 |
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-16027 has a medium severity rating, allowing attackers to access potentially sensitive user information.
To fix CVE-2020-16027, update Google Chrome to version 87.0.4280.66 or later.
Google Chrome versions prior to 87.0.4280.66 are affected by CVE-2020-16027.
Yes, malicious extensions can use CVE-2020-16027 to extract sensitive information from a user's disk.
Yes, there are indications that CVE-2020-16027 can be exploited if a user installs a malicious Chrome extension.