dbcve.org
ChromeWeb browser · Google

CVE-2020-6413

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
Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML validators 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 · moderate confidence

A vulnerability in the Blink rendering engine of Google Chrome allowed remote attackers to bypass HTML validators using crafted HTML pages. This inappropriate implementation flaw could enable injection attacks such as XSS by circumventing security validation checks that HTML validators are designed to enforce.

MitigationUpdate Google Chrome to version 80.0.3987.87 or later to apply the security patch. In enterprise environments, deploy the updated browser through centralized patch management systems.

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
Backports SleApplication
Affected:= 15.0

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 Google Chrome version
    Navigate to chrome://settings/help or use 'google-chrome --version' in terminal to display the current browser version
    Affected if Version number is less than 80.0.3987.87
  2. Verify Chrome package on OpenSUSE Backports
    On OpenSUSE systems, run 'rpm -qa | grep google-chrome' to list installed Chrome packages and their versions
    Affected if OpenSUSE Backports Sle 15.0 with Chrome version below 80.0.3987.87 is installed
  3. Confirm Blink engine presence
    This is inherent to Chrome - the Blink rendering engine is always present and cannot be disabled. No configuration check needed.
    Affected if Chrome is running at all (Blink is always active in vulnerable versions)

User is affected if Google Chrome version is below 80.0.3987.87 on any system, or if OpenSUSE Backports Sle 15.0 with an unpatched Chrome version is 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.

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 apply the security patch. In enterprise environments, deploy the updated browser through centralized patch management systems.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-6413 — 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-6413 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