CVE-2020-16024: Heap buffer overflow in UI
Published Nov 10, 2020
·Updated
Heap buffer overflow in UI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Credit
Sergei Glazunov(Google Project Zero)
Affected Software
4 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
Google Chrome OS
Event History
Nov 10, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:52 PM
Data Sourced
via MITRE·05:52 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-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 CVE-2020-16024?
CVE-2020-16024 is a heap buffer overflow vulnerability in the UI component of Google Chrome prior to version 87.0.4280.66.
2
How severe is CVE-2020-16024?
CVE-2020-16024 has a severity rating of 9.6, considered critical.
3
How can a remote attacker exploit CVE-2020-16024?
A remote attacker who has compromised the renderer process can potentially perform a sandbox escape by using a crafted HTML page.
4
Which versions of Google Chrome are affected by CVE-2020-16024?
Google Chrome versions prior to 87.0.4280.66 are affected by CVE-2020-16024.
5
How can I fix CVE-2020-16024?
To fix CVE-2020-16024, update Google Chrome to version 87.0.4280.66 or later.