CVE-2020-6471: 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
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Backports SLE=15.0-sp1
openSUSE Leap=15.1
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Remediation
Patch Available
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-6471?
CVE-2020-6471 has a high severity rating due to the potential for sandbox escape via malicious Chrome extensions.
2
How do I fix CVE-2020-6471?
To fix CVE-2020-6471, update Google Chrome or Chromium to version 83.0.4103.61 or higher.
3
What versions of Google Chrome are affected by CVE-2020-6471?
CVE-2020-6471 affects Google Chrome versions prior to 83.0.4103.61.
4
Can my system be exploited if it runs an affected version of Chromium related to CVE-2020-6471?
Yes, running an affected version of Chromium may allow an attacker to escape the sandbox through a malicious extension.
5
Is CVE-2020-6471 relevant for other operating systems?
Yes, CVE-2020-6471 affects various operating systems that run vulnerable versions of Google Chrome or Chromium.