CVE-2020-16031: Incorrect security UI in tab preview
Published Sep 29, 2020
·Updated
Insufficient data validation in UI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
Credit
wester0x01(https://twitter.com/wester0x01)
Affected Software
3 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<87.0.4280.66
87.0.4280.66
Google Chrome<87.0.4280.66
Event History
Sep 29, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-16018
- CVE-2020-16019
- CVE-2020-16020
- CVE-2020-16021
- CVE-2020-16022
- CVE-2020-16015
- CVE-2020-16014
- CVE-2020-16023
- CVE-2020-16024
- CVE-2020-16025
- CVE-2020-16045
- CVE-2020-16026
- CVE-2020-16027
- CVE-2020-16028
- CVE-2020-16029
- CVE-2020-16030
- CVE-2019-8075
- CVE-2020-16032
- CVE-2020-16033
- CVE-2020-16034
- CVE-2020-16035
- CVE-2020-16012
- CVE-2020-16036
Frequently Asked Questions
1
What is the severity of CVE-2020-16031?
CVE-2020-16031 has been classified as a medium severity vulnerability due to the potential for remote attackers to spoof URL information in the browser's Omnibox.
2
How do I fix CVE-2020-16031?
To resolve CVE-2020-16031, update Google Chrome to version 87.0.4280.66 or later.
3
Which versions of Chrome are affected by CVE-2020-16031?
CVE-2020-16031 impacts all versions of Google Chrome prior to 87.0.4280.66.
4
What type of attacks can exploit CVE-2020-16031?
CVE-2020-16031 can be exploited through crafted HTML pages that spoof the contents of the Omnibox.
5
Is there a workaround for CVE-2020-16031 if I can't update Chrome?
There are no recommended workarounds for CVE-2020-16031; upgrading Google Chrome is the best and only mitigation.