CVE-2020-6562: Insufficient policy enforcement in Blink
Published May 27, 2020
·Updated
Insufficient policy enforcement in Blink in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
Masato Kinugawa
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<85.0.4183.83
85.0.4183.83
Google Chrome<85.0.4183.83
openSUSE Backports SLE=15.0-sp1
openSUSE Backports SLE=15.0-sp2
Debian Debian Linux=10.0
Fedoraproject Fedora=33
openSUSE Leap=15.1
openSUSE Leap=15.2
Event History
May 27, 2020
CVE Published
12:00 AM
Sep 21, 2020
CVE Published
via MITRE·07:06 PM
Data Sourced
via MITRE·07:06 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2020-6562?
CVE-2020-6562 is classified as a high severity vulnerability.
2
How do I fix CVE-2020-6562?
To fix CVE-2020-6562, update Google Chrome to version 85.0.4183.83 or later.
3
What types of software are affected by CVE-2020-6562?
CVE-2020-6562 affects multiple versions of Google Chrome and Chromium across various operating systems.
4
Can CVE-2020-6562 lead to data exposure?
Yes, CVE-2020-6562 allows attackers to leak cross-origin data via a crafted HTML page.
5
What is the main cause of CVE-2020-6562?
CVE-2020-6562 is caused by insufficient policy enforcement in the Blink engine of Google Chrome.