CVE-2020-6470: XSS
Published May 21, 2020
·Updated
Insufficient validation of untrusted input in clipboard in Google Chrome prior to 83.0.4103.61 allowed a local attacker to inject arbitrary scripts or HTML (UXSS) via crafted clipboard contents.
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
Fedoraproject Fedora=31
Fedoraproject Fedora=32
openSUSE Backports SLE=15.0-sp1
openSUSE Leap=15.1
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Remediation
Patch Available
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-6470?
CVE-2020-6470 is considered a medium severity vulnerability due to potential UXSS exploitation.
2
How do I fix CVE-2020-6470?
To fix CVE-2020-6470, update Google Chrome or Chromium to version 83.0.4103.61 or later.
3
What impact does CVE-2020-6470 have on users?
CVE-2020-6470 allows local attackers to inject arbitrary scripts or HTML into the browser via crafted clipboard content.
4
Which versions of Google Chrome are affected by CVE-2020-6470?
Google Chrome versions prior to 83.0.4103.61 are affected by CVE-2020-6470.
5
Is there a specific platform affected by CVE-2020-6470?
CVE-2020-6470 affects multiple platforms including Debian, Fedora, and openSUSE installations of Google Chrome and Chromium.