CVE-2020-16018: Use after free in payments
Published Oct 7, 2020
·Updated
Use after free in payments 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
Man Yue Mo(GitHub Security 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
Oct 7, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:50 PM
Data Sourced
via MITRE·05:50 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- 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-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-16018?
CVE-2020-16018 has been classified as a high severity vulnerability.
2
How do I fix CVE-2020-16018?
To fix CVE-2020-16018, upgrade to Chromium version 90.0.4430.212-1~deb10u1 or later.
3
What type of vulnerability is CVE-2020-16018?
CVE-2020-16018 is identified as a use after free vulnerability in Google Chrome.
4
Can CVE-2020-16018 lead to a sandbox escape?
Yes, CVE-2020-16018 could allow a remote attacker to perform a sandbox escape.
5
Which products are affected by CVE-2020-16018?
CVE-2020-16018 affects Google Chrome versions prior to 87.0.4280.66.