CVE-2020-6534: Buffer Overflow
Published Jul 22, 2020
·Updated
Heap buffer overflow in WebRTC 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-6534?
CVE-2020-6534 has been classified as a high severity vulnerability because it allows a remote attacker to potentially exploit heap corruption.
2
How do I fix CVE-2020-6534?
To mitigate CVE-2020-6534, users should update to the latest version of Google Chrome or the affected Chromium-based browsers.
3
Which versions of Google Chrome are affected by CVE-2020-6534?
CVE-2020-6534 affects Google Chrome versions prior to 84.0.4147.89.
4
What kind of attack can CVE-2020-6534 facilitate?
CVE-2020-6534 can facilitate remote code execution through heap buffer overflow via a crafted HTML page.
5
Which operating systems are impacted by CVE-2020-6534?
CVE-2020-6534 impacts multiple operating systems including Debian, Fedora, and openSUSE.