dbcve.org
ChromeWeb browser · Google

CVE-2020-6407

HIGH · 8.8 CVSS v3.1 Published 2020-02-27
Fix available
A fix is available. Upgrade to 80.0.3987.122 or later.
See remediation →
95/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
Out of bounds memory access in streams in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially exploit heap corruption 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

Out of bounds memory access in Google Chrome's streams component allows remote attackers to exploit heap corruption via specially crafted HTML pages, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 80.0.3987.122 or later to patch the vulnerability.

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:< 80.0.3987.122

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Confirm Google Chrome is installed
    Check if Google Chrome browser is present on the system. Look for Chrome in installed programs (Windows), Applications folder (macOS), or package manager (Linux). Note: Chromium or other Chromium-based browsers are NOT the same product.
    Affected if The system has Google Chrome installed as the primary browser
  2. Locate Chrome executable and determine version
    In Chrome, navigate to chrome://settings/help or click Help > About Google Chrome. Alternatively, run 'google-chrome --version' from command line (Linux) or find the Chrome binary and check its properties.
    Affected if Unable to determine the installed version
  3. Compare installed version to affected range
    Note the full version number displayed (e.g., 80.0.3987.87). Compare it numerically against 80.0.3987.122. Any version BEFORE 80.0.3987.122 is affected.
    Affected if Installed version is less than 80.0.3987.122 (e.g., 79.x.x.x, 78.x.x.x, etc.)
  4. Verify the streams component is accessible
    This vulnerability is triggered via the streams API in Google Chrome. No special configuration check is needed - the vulnerability exists in the core Chrome streams component for affected versions.
    Affected if Running an affected version means the streams component contains the out-of-bounds flaw

If Google Chrome is installed and its version is below 80.0.3987.122, the environment is vulnerable to this CVE.

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.

From vendor data
Upgrade available Upgrade to 80.0.3987.122 or later
Fixed in 80.0.3987.122
Interim mitigation

Update Google Chrome to version 80.0.3987.122 or later to patch the vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6407 — 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-6407 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