CVE-2020-16015: Insufficient data validation in WASM
Published Nov 7, 2020
·Updated
Insufficient data validation in WASM in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit
Rong Jian(360 Alpha Lab), Leecraso(360 Alpha Lab)
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
Nov 7, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:49 PM
Data Sourced
via MITRE·05:49 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-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-16031
- 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-16015?
CVE-2020-16015 has a medium severity rating due to potential heap corruption vulnerabilities.
2
How do I fix CVE-2020-16015?
To mitigate CVE-2020-16015, update your Google Chrome or Chromium to version 87.0.4280.66 or later.
3
Which versions of Google Chrome are affected by CVE-2020-16015?
CVE-2020-16015 affects Google Chrome versions prior to 87.0.4280.66.
4
How can attackers exploit CVE-2020-16015?
Attackers can exploit CVE-2020-16015 through a crafted HTML page leading to potential heap corruption.
5
What types of systems are impacted by CVE-2020-16015?
CVE-2020-16015 impacts users of Google Chrome and Chromium running on affected versions.