dbcve.org
ChromeWeb browser · Google

CVE-2020-16015

HIGH · 8.8 CVSS v3.1 Published 2021-01-08
Fix available
A fix is available. Upgrade to 87.0.4280.66 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
Insufficient data validation in WASM in Google Chrome prior to 87.0.4280.66 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

Insufficient data validation in WebAssembly (WASM) in Google Chrome prior to version 87.0.4280.66 allows remote attackers to exploit heap corruption via a crafted HTML page.

MitigationUpdate Google Chrome to version 87.0.4280.66 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:< 87.0.4280.66

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. Verify Google Chrome is installed
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' in terminal, or check Help > About Google Chrome in the application menu
    Affected if Google Chrome is not installed - this CVE does not apply
  2. Determine installed Chrome version
    Note the full version number displayed in chrome://version or from the version command output
    Affected if Unable to determine version - cannot assess exposure
  3. Compare version against affected range
    Compare the installed version number to 87.0.4280.66. Any version starting with numbers lower than 87 (such as 86.x, 85.x, etc.) or any 87.x version below 87.0.4280.66 is vulnerable
    Affected if Installed version is less than 87.0.4280.66 (for example, 86.0.4240.75 or 87.0.4280.40)
  4. Confirm WebAssembly is enabled (default state)
    Navigate to chrome://flags in Chrome and search for 'WebAssembly'. The feature is enabled by default in affected versions
    Affected if WebAssembly is enabled (default) - exploitation possible; if disabled, the attack surface is reduced but updating is still recommended

User is affected if Google Chrome is installed with any version lower than 87.0.4280.66 and WebAssembly is in its default enabled state.

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

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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