CVE-2020-6533: High severity google chrome vulnerability
Published Jul 22, 2020
·Updated
Type Confusion in V8 in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected Software
8 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<84.0.4147.89
openSUSE Backports SLE=15.0-sp1
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Leap=15.1
openSUSE Leap=15.2
Event History
Jul 22, 2020
CVE Published
via MITRE·04:16 PM
Data Sourced
via MITRE·04:16 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6533?
CVE-2020-6533 has a critical severity level due to its potential for exploitation through heap corruption.
2
How do I fix CVE-2020-6533?
To fix CVE-2020-6533, update your affected version of Google Chrome or Chromium to a version that is 84.0.4147.89 or later.
3
Which versions of Google Chrome are affected by CVE-2020-6533?
Google Chrome versions prior to 84.0.4147.89 are affected by CVE-2020-6533.
4
Is CVE-2020-6533 specific to certain operating systems?
Yes, CVE-2020-6533 affects multiple operating systems including Debian, Fedora, and openSUSE.
5
What is the potential impact of exploiting CVE-2020-6533?
Exploiting CVE-2020-6533 could lead to remote code execution due to heap corruption.