CVE-2020-6530: High severity google chrome vulnerability
Published Jul 22, 2020
·Updated
Out of bounds memory access in developer tools in Google Chrome prior to 84.0.4147.89 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension.
Affected Software
9 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
openSUSE Backports SLE=15.0-sp2
openSUSE Leap=15.1
openSUSE Leap=15.2
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Debian Debian Linux=10.0
Remediation
Patch Available
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-6530?
CVE-2020-6530 has a severity rating that indicates potential for exploitation via heap corruption.
2
How do I fix CVE-2020-6530?
To fix CVE-2020-6530, update to Google Chrome version 84.0.4147.89 or later.
3
What versions of Google Chrome are affected by CVE-2020-6530?
CVE-2020-6530 affects Google Chrome versions prior to 84.0.4147.89.
4
Can a malicious extension exploit CVE-2020-6530?
Yes, a malicious extension can exploit CVE-2020-6530 by causing out of bounds memory access.
5
What types of systems are impacted by CVE-2020-6530?
CVE-2020-6530 impacts systems using vulnerable versions of Google Chrome and Chromium.