First published: Wed 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: chrome-cve-admin@google.com Masato Kinugawa
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 | <85.0.4183.83 | 85.0.4183.83 |
Google Chrome | <85.0.4183.83 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE Backports | =15.0-sp2 | |
Debian | =10.0 | |
Fedora | =33 | |
openSUSE | =15.1 | |
openSUSE | =15.2 |
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-6562 is classified as a high severity vulnerability.
To fix CVE-2020-6562, update Google Chrome to version 85.0.4183.83 or later.
CVE-2020-6562 affects multiple versions of Google Chrome and Chromium across various operating systems.
Yes, CVE-2020-6562 allows attackers to leak cross-origin data via a crafted HTML page.
CVE-2020-6562 is caused by insufficient policy enforcement in the Blink engine of Google Chrome.