First published: Tue May 19 2020(Updated: )
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.
Credit: chrome-cve-admin@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome | <83.0.4103.61 | 83.0.4103.61 |
Google Chrome | <83.0.4103.61 | |
openSUSE Backports | =15.0-sp1 | |
Debian | =9.0 | |
Debian | =10.0 | |
Fedora | =31 | |
Fedora | =32 | |
openSUSE | =15.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-6465 has been classified as a high severity vulnerability due to its potential for remote exploitation.
To fix CVE-2020-6465, users should update their Google Chrome or Chromium to version 83.0.4103.61 or later.
CVE-2020-6465 affects Google Chrome on Android and various versions of Chromium across different Linux distributions.
Yes, CVE-2020-6465 allows a compromised renderer process to potentially perform a sandbox escape.
There are no known workarounds for CVE-2020-6465; updating to a fixed version is the recommended action.