CVE-2020-6535: XSS
Published Jul 22, 2020
·Updated
Insufficient data validation in WebUI in Google Chrome prior to 84.0.4147.89 allowed a remote attacker who had compromised the renderer process to inject scripts or HTML into a privileged page 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-6535?
CVE-2020-6535 has been classified as a high severity vulnerability.
2
How do I fix CVE-2020-6535?
To fix CVE-2020-6535, upgrade Google Chrome to version 84.0.4147.89 or later.
3
What types of attacks are possible with CVE-2020-6535?
CVE-2020-6535 allows remote attackers to inject scripts or HTML into a privileged page.
4
Which versions of Google Chrome are affected by CVE-2020-6535?
Google Chrome versions prior to 84.0.4147.89 are affected by CVE-2020-6535.
5
What platforms are impacted by the CVE-2020-6535 vulnerability?
CVE-2020-6535 impacts multiple platforms including Debian, Fedora, and openSUSE.