CVE-2020-6413: High severity Google Chrome vulnerability
An inappropriate implementation flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1005713
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML validators 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.87Patch 1005713
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6413?
CVE-2020-6413 has been classified as a high severity vulnerability.
How do I fix CVE-2020-6413?
To fix CVE-2020-6413, update your Chromium or Google Chrome browser to the latest version listed in the remediation section.
What products are affected by CVE-2020-6413?
CVE-2020-6413 affects various versions of Chromium, Google Chrome, and specifically the chromium-browser package on Red Hat.
Who reported CVE-2020-6413?
CVE-2020-6413 was reported through upstream bug tracking of the Chromium project.
What type of flaw is described in CVE-2020-6413?
CVE-2020-6413 describes an inappropriate implementation flaw found in the Blink component of the Chromium browser.