dbcve.org
ChromeWeb browser · Google

CVE-2020-6573

CRITICAL · 9.6 CVSS v3.1 Published 2020-09-21
Fix available
A fix is available. Upgrade to 85.0.4183.102 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in video in Google Chrome on Android prior to 85.0.4183.102 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 confidence

A use-after-free vulnerability exists in the video component of Google Chrome on Android versions prior to 85.0.4183.102. An attacker who has already compromised the renderer process can exploit this memory corruption flaw to potentially escape the sandbox isolation via a specially crafted HTML page.

MitigationUpdate Google Chrome for Android to version 85.0.4183.102 or later to patch the vulnerability. Organizations should ensure mobile device management policies enforce Chrome updates on managed devices.

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
Affected:< 85.0.4183.102
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 31= 33
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1= 15.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Google Chrome is installed on Android
    On the Android device, open Chrome, tap the three-dot menu, go to Settings, and look for Chrome version in the 'About Chrome' section. Alternatively, check via ADB with: adb shell dumpsys package com.android.chrome | grep versionName
    Affected if Chrome for Android is installed and the version shown is less than 85.0.4183.102
  2. Identify if Google Chrome is installed on Linux systems
    On Debian-based systems: dpkg -l | grep google-chrome. On RPM-based systems (Fedora): rpm -qa | grep google-chrome. On openSUSE: rpm -qa | grep google-chrome
    Affected if Google Chrome is installed and the version is less than 85.0.4183.102
  3. Retrieve the exact Chrome version number
    On Linux, run: google-chrome --version or /opt/google/chrome/chrome --version. On Android, the version appears in About Chrome (e.g., 85.0.4183.81)
    Affected if The returned version number is lower than 85.0.4183.102
  4. Verify the video component is accessible
    Confirm Chrome can load and render video content by visiting any video-enabled webpage. The vulnerability exists in the video component, so video playback capability must be present
    Affected if Chrome can play video and the version is below 85.0.4183.102

You are affected if Google Chrome (on Android or Linux) is installed with a version number lower than 85.0.4183.102 and video playback functionality is available.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 85.0.4183.102 or later
Fixed in 85.0.4183.102
Interim mitigation

Update Google Chrome for Android to version 85.0.4183.102 or later to patch the vulnerability. Organizations should ensure mobile device management policies enforce Chrome updates on managed devices.

Recommended fix High confidence

Chrome 85.0.4183.102 or later; vendor-specific patched packages for Linux distributions

  1. Check current Chrome/Chromium version by navigating to chrome://settings/help
  2. Update Chrome to version 85.0.4183.102 or later via the built-in updater or from official.google.com/chrome
  3. For Linux distributions (Debian 10, Fedora 31/33, SLE 15, openSUSE Leap 15.1/15.2), apply vendor security updates via system package manager (e.g., apt update && apt upgrade, dnf update, zypper patch)
Caveat None expected - this is a security patch with minimal functional changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6573 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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