CVE-2020-6491: Medium severity google chrome vulnerability
Published May 21, 2020
·Updated
Insufficient data validation in site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted domain name.
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<83.0.4103.61
openSUSE Backports SLE=15.0-sp1
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Leap=15.1
Event History
May 21, 2020
CVE Published
via MITRE·03:46 AM
Data Sourced
via MITRE·03:46 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6491?
CVE-2020-6491 is classified as a high severity vulnerability due to its potential to spoof security UI.
2
How do I fix CVE-2020-6491?
To mitigate CVE-2020-6491, update Google Chrome or Chromium to version 83.0.4103.61 or later.
3
Which versions of software are affected by CVE-2020-6491?
CVE-2020-6491 affects Google Chrome versions prior to 83.0.4103.61 and certain versions of Chromium.
4
Is CVE-2020-6491 a client-side or server-side vulnerability?
CVE-2020-6491 is a client-side vulnerability affecting web browsers.
5
What type of attack is possible with CVE-2020-6491?
CVE-2020-6491 allows a remote attacker to spoof security UI through a crafted domain name.