dbcve.org
ChromeWeb browser · Google

CVE-2020-6389

HIGH · 8.8 CVSS v3.1 Published 2020-02-11
Fix available
A fix is available. Upgrade to 80.0.3987.87 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 write in WebRTC in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap corruption via a crafted video stream.

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 write vulnerability in WebRTC's video handling component in Google Chrome versions prior to 80.0.3987.87 allows heap corruption when processing a specially crafted video stream, potentially enabling remote code execution.

MitigationUpdate Google Chrome to version 80.0.3987.87 or later to patch the WebRTC out-of-bounds write 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.87

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. Check installed Chrome version
    Navigate to chrome://settings/help or enter chrome://version in the address bar. The version number is displayed on the page.
    Affected if Version is less than 80.0.3987.87 (e.g., 79.x.x.x or earlier)
  2. Verify WebRTC is enabled
    Navigate to chrome://settings/content in Chrome or check via Group Policy: Computer Configuration > Administrative Templates > Google Chrome > WebRTC. WebRTC is typically enabled by default.
    Affected if WebRTC is enabled (this is the default state)
  3. Check Chrome channel for update availability
    Navigate to chrome://settings/help and look at the channel indicator (Stable, Beta, Dev, Canary). You can also check via registry key: HKLM\SOFTWARE\Policies\Google\Chrome\VersionSelectorUpdateURL or HKCU\Software\Google\Chrome\BLBeacon\version
    Affected if Channel is not Stable or version is not 80.0.3987.87 or higher
  4. Confirm WebRTC video processing is in use
    The vulnerability triggers when processing a specially crafted video stream via WebRTC. Check for active WebRTC sessions or test by making a WebRTC-based call (e.g., Google Meet, WebRTC test pages).
    Affected if WebRTC video streams are being processed while running an affected Chrome version

You are affected if Google Chrome version is below 80.0.3987.87 and WebRTC is enabled (default state), as the vulnerability exists in the WebRTC video handling component.

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.87 or later
Fixed in 80.0.3987.87
Interim mitigation

Update Google Chrome to version 80.0.3987.87 or later to patch the WebRTC out-of-bounds write 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-6389 — 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-6389 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