CVE-2020-6469: Critical severity google chrome vulnerability
Published May 21, 2020
·Updated
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension.
Affected Software
8 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
Google Chrome<83.0.4103.61
openSUSE Backports SLE=15.0-sp1
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Leap=15.1
Event History
May 21, 2020
CVE Published
via MITRE·03:46 AM
Data Sourced
via MITRE·03:46 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6469?
The severity of CVE-2020-6469 is categorized as high due to potential sandbox escape vulnerabilities.
2
How do I fix CVE-2020-6469?
To fix CVE-2020-6469, update Google Chrome or Chromium to version 83.0.4103.61 or later.
3
What platforms are affected by CVE-2020-6469?
CVE-2020-6469 affects multiple platforms including Debian, Fedora, and openSUSE distributions.
4
Can CVE-2020-6469 be exploited remotely?
Yes, CVE-2020-6469 can be exploited by convincing a user to install a malicious Chrome extension.
5
What does CVE-2020-6469 exploit in Google Chrome?
CVE-2020-6469 exploits insufficient policy enforcement in developer tools within Google Chrome.