CVE-2020-6465: Use After Free
Use after free in reader mode in Google Chrome on Android prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-6466
- CVE-2020-6467
- CVE-2020-6468
- CVE-2020-6469
- CVE-2020-6470
- CVE-2020-6471
- CVE-2020-6472
- CVE-2020-6473
- CVE-2020-6474
- CVE-2020-6475
- CVE-2020-6476
- CVE-2020-6477
- CVE-2020-6478
- CVE-2020-6479
- CVE-2020-6480
- CVE-2020-6481
- CVE-2020-6482
- CVE-2020-6483
- CVE-2020-6484
- CVE-2020-6485
- CVE-2020-6486
- CVE-2020-6487
- CVE-2020-6488
- CVE-2020-6489
- CVE-2020-6490
- CVE-2020-6491
Frequently Asked Questions
What is the severity of CVE-2020-6465?
CVE-2020-6465 has been classified as a high severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2020-6465?
To fix CVE-2020-6465, users should update their Google Chrome or Chromium to version 83.0.4103.61 or later.
What types of systems are affected by CVE-2020-6465?
CVE-2020-6465 affects Google Chrome on Android and various versions of Chromium across different Linux distributions.
Can CVE-2020-6465 lead to a sandbox escape?
Yes, CVE-2020-6465 allows a compromised renderer process to potentially perform a sandbox escape.
Is there a workaround for CVE-2020-6465?
There are no known workarounds for CVE-2020-6465; updating to a fixed version is the recommended action.