CVE-2020-6522: Critical severity google chrome vulnerability
Published Jul 22, 2020
·Updated
Inappropriate implementation in external protocol handlers in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.
Affected Software
9 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<84.0.4147.89
openSUSE Backports SLE=15.0-sp1
openSUSE Backports SLE=15.0-sp2
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Leap=15.1
openSUSE Leap=15.2
Event History
Jul 22, 2020
CVE Published
via MITRE·04:16 PM
Data Sourced
via MITRE·04:16 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6522?
CVE-2020-6522 is considered a high severity vulnerability due to its potential for sandbox escape.
2
How do I fix CVE-2020-6522?
To fix CVE-2020-6522, update Google Chrome to version 84.0.4147.89 or later.
3
Which versions of Google Chrome are affected by CVE-2020-6522?
Google Chrome versions prior to 84.0.4147.89 are affected by CVE-2020-6522.
4
Can CVE-2020-6522 be exploited remotely?
Yes, CVE-2020-6522 can potentially be exploited by an attacker through a crafted HTML page.
5
What platforms are impacted by CVE-2020-6522?
CVE-2020-6522 impacts multiple platforms including Debian, Fedora, and openSUSE that use affected versions of Chrome.