CVE-2020-6510: Buffer Overflow

Q: What is the severity of CVE-2020-6510?

CVE-2020-6510 has been classified as a high severity vulnerability due to its potential for remote code execution.

Q: How do I fix CVE-2020-6510?

To fix CVE-2020-6510, you need to update Google Chrome or Chromium to version 84.0.4147.89 or later.

Q: Which versions of Google Chrome are affected by CVE-2020-6510?

All versions of Google Chrome prior to 84.0.4147.89 are affected by CVE-2020-6510.

Q: Can CVE-2020-6510 be exploited remotely?

Yes, CVE-2020-6510 can be exploited remotely through a crafted HTML page.

Q: What types of systems are affected by CVE-2020-6510?

CVE-2020-6510 affects systems running affected versions of Google Chrome and Chromium across various operating systems.

Published Jul 14, 2020

Updated

Heap buffer overflow in background fetch 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

10 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

84.0.4147.89

Google Chrome<84.0.4147.89

openSUSE Backports SLE=15.0-sp1

openSUSE Backports SLE=15.0-sp2

Debian Debian Linux=10.0

Fedoraproject Fedora=31

Fedoraproject Fedora=32

openSUSE Leap=15.1

openSUSE Leap=15.2

Event History

Jul 14, 2020

CVE Published

12:00 AM

Jul 22, 2020

CVE Published

via MITRE·04:15 PM

Data Sourced

via MITRE·04:15 PM

DescriptionWeakness

Parent advisories

This vulnerability appears in the following advisories.

7394511674302395818

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

What is the severity of CVE-2020-6510?

CVE-2020-6510 has been classified as a high severity vulnerability due to its potential for remote code execution.

How do I fix CVE-2020-6510?