CVE-2020-6464: High severity google chrome vulnerability
Published May 21, 2020
·Updated
Type confusion in Blink in Google Chrome prior to 81.0.4044.138 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected Software
6 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<81.0.4044.138
Debian Debian Linux=9.0
Debian Debian Linux=10.0
openSUSE Leap=15.1
openSUSE Leap=15.2
Event History
May 21, 2020
CVE Published
via MITRE·03:46 AM
Data Sourced
via MITRE·03:46 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6464?
CVE-2020-6464 has been classified as a medium severity vulnerability.
2
How do I fix CVE-2020-6464?
To fix CVE-2020-6464, users should update Google Chrome and Chromium to the latest versions available.
3
Who is affected by CVE-2020-6464?
CVE-2020-6464 affects users of Google Chrome versions prior to 81.0.4044.138 and various versions of Chromium.
4
What type of vulnerability is CVE-2020-6464?
CVE-2020-6464 is a type confusion vulnerability in the Blink rendering engine of Google Chrome.
5
Can CVE-2020-6464 lead to remote code execution?
Yes, CVE-2020-6464 could potentially allow an attacker to exploit heap corruption and execute arbitrary code.