CVE-2020-6475: Medium severity google chrome vulnerability
Published May 21, 2020
·Updated
Incorrect implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI 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<83.0.4103.61
openSUSE Backports SLE=15.0-sp1
openSUSE Leap=15.1
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Debian Debian Linux=9.0
Debian Debian Linux=10.0
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-6475?
CVE-2020-6475 has been classified as a high severity vulnerability due to its potential to allow a remote attacker to spoof security UI in Google Chrome.
2
What versions of Google Chrome are affected by CVE-2020-6475?
Google Chrome versions prior to 83.0.4103.61 are affected by CVE-2020-6475.
3
How do I fix CVE-2020-6475?
To fix CVE-2020-6475, users should upgrade to Google Chrome version 83.0.4103.61 or later.
4
Can CVE-2020-6475 affect other software apart from Google Chrome?
Yes, CVE-2020-6475 can also affect affected versions of Chromium and various Linux distributions running vulnerable versions of the browser.
5
What is the main impact of CVE-2020-6475?
The main impact of CVE-2020-6475 is the ability for remote attackers to spoof the security user interface through crafted HTML pages.