dbcve.org
ChromeWeb browser · Google

CVE-2020-6414

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
Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass navigation restrictions 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

This is a client-side vulnerability in Google Chrome's Safe Browsing feature. The insufficient policy enforcement allowed a remote attacker to bypass navigation restrictions through a crafted HTML page, potentially enabling malicious site redirection or navigation to unsafe websites despite Safe Browsing protections.

MitigationUpdate Google Chrome to version 80.0.3987.87 or later. For enterprise environments, deploy the Chrome update via standard patch management processes and verify Safe Browsing protection is functioning.

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. Determine installed Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the exact version number
    Affected if The installed version is lower than 80.0.3987.87 (e.g., 79.x or earlier)
  2. Check if Safe Browsing protection is active
    Navigate to chrome://settings/security and verify that 'Safe Browsing' is turned on in the privacy settings
    Affected if Safe Browsing is enabled AND the Chrome version is below 80.0.3987.87 - the bypass only affects users with Safe Browsing protection active
  3. Verify operating system for OpenSUSE users
    Check if the system is running OpenSUSE Backports Sle 15.0 specifically by running 'cat /etc/os-release' or 'hostnamectl'
    Affected if Running OpenSUSE Backports Sle version 15.0 with an affected Chrome version below 80.0.3987.87

You are affected if you run Google Chrome version below 80.0.3987.87 with Safe Browsing protection enabled, or are on OpenSUSE Backports Sle 15.0 with an older Chrome version.

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. For enterprise environments, deploy the Chrome update via standard patch management processes and verify Safe Browsing protection is functioning.

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