CVE-2020-6393: Medium severity Google Chrome vulnerability
An insufficient policy enforcement flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1035058
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 90.0.4430.212-1~deb10u1Fixed in 116.0.5845.180-1~deb11u1Fixed in 120.0.6099.129-1~deb11u1Fixed in 119.0.6045.199-1~deb12u1Fixed in 120.0.6099.129-1~deb12u1Fixed in 120.0.6099.129-1 - Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 80.0.3987.87 - Upgrade
Upgrade
chromium/google chrome (Blink)to a version that resolves this vulnerability.Fixed in 80.0.3987.87
Event History
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2020-6393.
What is the title of this vulnerability?
The title of this vulnerability is 'Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.'
What is the severity of CVE-2020-6393?
The severity of CVE-2020-6393 is medium with a CVSS score of 6.5.
How can I fix CVE-2020-6393?
To fix CVE-2020-6393, update your Google Chrome browser to version 80.0.3987.87 or later.
Where can I find more information about CVE-2020-6393?
You can find more information about CVE-2020-6393 in the following references: [reference 1](https://code.google.com/p/chromium/issues/detail?id=1035058), [reference 2](https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html), [reference 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1801839).