CVE-2020-6430: High severity Google Chrome vulnerability
Type Confusion in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption 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
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6430?
CVE-2020-6430 has been classified as a high severity vulnerability due to its potential for exploitation leading to heap corruption.
How do I fix CVE-2020-6430?
To resolve CVE-2020-6430, update your Google Chrome or Chromium browser to version 81.0.4044.92 or later.
What versions of Google Chrome are affected by CVE-2020-6430?
CVE-2020-6430 affects Google Chrome versions prior to 81.0.4044.92.
Is my system at risk if I use an outdated version of Chromium regarding CVE-2020-6430?
Yes, using outdated versions of Chromium below 81.0.4044.92 poses a risk of exploitation via CVE-2020-6430.
Which operating systems are impacted by CVE-2020-6430?
CVE-2020-6430 impacts several operating systems including Debian, Fedora, and openSUSE when running vulnerable versions of Google Chrome or Chromium.