dbcve.org
ChromeWeb browser · Google

CVE-2020-6466

CRITICAL · 9.6 CVSS v3.1 Published 2020-05-21
Fix available
A fix is available. Upgrade to 83.0.4103.61 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 media in Google Chrome 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 confidence

Use-after-free vulnerability in Chrome's media component prior to version 83.0.4103.61 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox and execute arbitrary code via a crafted HTML page.

MitigationUpdate Google Chrome to version 83.0.4103.61 or later. Organizations should deploy browser updates through their patch management systems and verify completion across affected endpoints.

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:< 83.0.4103.61
Debian LinuxOperating system
Affected:= 9.0= 10.0
FedoraOperating system
Affected:= 31= 32
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1

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. Check Google Chrome version
    Navigate to chrome://version or run 'google-chrome --version' in terminal
    Affected if Version is earlier than 83.0.4103.61
  2. Verify Linux distribution version for Debian
    Run 'cat /etc/debian_version' or 'lsb_release -a'
    Affected if Running Debian 9.0 or 10.0 with vulnerable Chrome version installed
  3. Verify Linux distribution version for Fedora
    Run 'cat /etc/fedora-release' or 'hostnamectl'
    Affected if Running Fedora 31 or 32 with vulnerable Chrome version installed
  4. Verify Linux distribution version for OpenSUSE
    Run 'cat /etc/os-release' or 'lsb_release -a'
    Affected if Running OpenSUSE Leap 15.1 or OpenSUSE Backports SLE 15.0 with vulnerable Chrome version installed
  5. Confirm media component is in use
    The vulnerability is in Chrome's media component; ensure the Chrome browser or chromium-based browser is actively used and not headless-only
    Affected if Browser with vulnerable version is actively used and renderer process can be engaged

User is affected if running any Google Chrome version prior to 83.0.4103.61, or any of the listed Linux distributions with the vulnerable Chrome version installed.

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 83.0.4103.61 or later
Fixed in 83.0.4103.61
Interim mitigation

Update Google Chrome to version 83.0.4103.61 or later. Organizations should deploy browser updates through their patch management systems and verify completion across affected endpoints.

Recommended fix High confidence

Chrome 83.0.4103.61 or later

  1. Check current Chrome version by navigating to chrome://settings/help or running `google-chrome --version` in terminal
  2. For Debian/Ubuntu: Run `sudo apt-get update && sudo apt-get upgrade google-chrome-stable` to install the latest version
  3. For Fedora: Run `sudo dnf update google-chrome-stable` to install the latest version
  4. For SUSE/openSUSE: Run `sudo zypper update google-chrome-stable` to install the latest version
  5. Alternatively, download Chrome 83.0.4103.61 or later directly from https://www.google.com/chrome/
  6. Restart Chrome browser after updating to apply the security patch

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-6466 — 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-6466 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