CVE-2020-6529: Medium severity google chrome vulnerability
Published Jul 22, 2020
·Updated
Inappropriate implementation in WebRTC in Google Chrome prior to 84.0.4147.89 allowed an attacker in a privileged network position to leak cross-origin data 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
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Leap=15.1
openSUSE Leap=15.2
openSUSE Backports SLE=15.0-sp2
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-6529?
CVE-2020-6529 is considered a medium severity vulnerability as it allows data leakage in privileged network positions.
2
How do I fix CVE-2020-6529?
To fix CVE-2020-6529, update Google Chrome or Chromium to version 84.0.4147.89 or later.
3
Who is affected by CVE-2020-6529?
CVE-2020-6529 affects Google Chrome and Chromium users on versions prior to 84.0.4147.89.
4
What does CVE-2020-6529 exploit?
CVE-2020-6529 exploits an inappropriate implementation of WebRTC in Google Chrome.
5
Can CVE-2020-6529 lead to denial of service?
No, CVE-2020-6529 specifically leads to the leakage of cross-origin data, not denial of service.