CVE-2020-6521: Medium severity google chrome vulnerability
Published Jul 22, 2020
·Updated
Side-channel information leakage in autofill in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
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
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-6521?
CVE-2020-6521 is classified as high severity due to its potential for exposing sensitive information.
2
How do I fix CVE-2020-6521?
To fix CVE-2020-6521, upgrade your Google Chrome or Chromium browser to the latest version that is 84.0.4147.89 or later.
3
What software is affected by CVE-2020-6521?
CVE-2020-6521 affects Google Chrome versions prior to 84.0.4147.89 and specific versions of Chromium on Debian and openSUSE.
4
Can CVE-2020-6521 be exploited remotely?
Yes, CVE-2020-6521 can be exploited remotely through a crafted HTML page.
5
What type of vulnerability is CVE-2020-6521?
CVE-2020-6521 is a side-channel information leakage vulnerability.