ChromeWeb browser · Google
CVE-2020-6465
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability exists in Google Chrome's reader mode on Android versions prior to 83.0.4103.61. An attacker who has already compromised the renderer process (through other means) can exploit this memory corruption issue via a crafted HTML page to potentially escape the browser's sandbox and execute code at a higher privilege level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 83.0.4103.61
Debian LinuxOperating system
= 9.0= 10.0
FedoraOperating system
= 31= 32= 15.0= 15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Chrome for Android is installedOn the Android device, go to Settings > Apps > Google Chrome. If Chrome appears in the app list, it is installed.Affected if Google Chrome for Android is installed on the device
-
Check the installed Chrome versionIn Settings > Apps > Google Chrome > App info, look at the Version number. Compare this against 83.0.4103.61Affected if The installed version is lower than 83.0.4103.61 (for example, 83.0.4103.60 or earlier)
-
Confirm Chrome is running on AndroidVerify the operating system of the device is Android. This vulnerability affects Chrome specifically on Android, not iOS or other platforms.Affected if The Chrome browser is running on an Android device (any Android version)
-
Verify reader mode functionality existsIn Chrome for Android, open any webpage and look for the 'Reader mode' icon in the address bar (triangle with lines icon). If it is present, reader mode is available.Affected if Reader mode is accessible and can be triggered on the Chrome for Android installation
A user is affected if Chrome for Android is installed with a version lower than 83.0.4103.61 and reader mode feature is present on the device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped83.0.4103.61
Update Google Chrome for Android to version 83.0.4103.61 or later. Organizations should ensure auto-updates are enabled or deploy the patched version to managed Android devices.
Chrome 83.0.4103.61 or later (or latest available)
- Update Google Chrome for Android to version 83.0.4103.61 or later
- If using system-packaged Chromium on Linux (Debian, Fedora, SUSE Leap), update the chromium package to the latest available version in your distribution's repositories
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6465 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data