CVE-2020-6513: Buffer Overflow
Published Jul 22, 2020
·Updated
Heap buffer overflow in PDFium in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.
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
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-6513?
CVE-2020-6513 is considered a high severity vulnerability due to the potential for remote exploitation via crafted PDF files.
2
How do I fix CVE-2020-6513?
To fix CVE-2020-6513, update Google Chrome or Chromium to version 84.0.4147.89 or later.
3
What is CVE-2020-6513?
CVE-2020-6513 is a heap buffer overflow vulnerability in PDFium in Google Chrome that can lead to heap corruption.
4
Which software is affected by CVE-2020-6513?
CVE-2020-6513 affects versions of Google Chrome prior to 84.0.4147.89 and various versions of Chromium on specific distributions.
5
Can CVE-2020-6513 be exploited remotely?
Yes, CVE-2020-6513 can be exploited remotely if a user opens a specially crafted PDF file.