dbcve.org
ChromeWeb browser · Google

CVE-2020-15980

HIGH · 7.8 CVSS v3.1 Published 2020-11-03
Fix available
A fix is available. Upgrade to 86.0.4240.75 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 Intents in Google Chrome on Android prior to 86.0.4240.75 allowed a local attacker to bypass navigation restrictions via crafted Intents.

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 policy enforcement in Chrome on Android's Intent handling allows a local attacker to bypass navigation restrictions by crafting malicious Intents. This could enable a malicious app or an attacker with physical device access to redirect users to arbitrary URLs or perform actions outside Chrome's intended security boundaries.

MitigationUpdate Google Chrome on Android to version 86.0.4240.75 or later to patch the Intent policy enforcement 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:< 86.0.4240.75
FedoraOperating system
Affected:= 31= 32= 33
Debian LinuxOperating system
Affected:= 10.0
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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 if Google Chrome is installed
    On Android, go to Settings > Apps > Chrome to verify Chrome is installed. On desktop Linux, run 'google-chrome --version' or check your package manager.
    Affected if Chrome browser is installed on the device or system
  2. Determine Chrome version on Android
    Open Chrome app, tap the three-dot menu > Settings > About Chrome to view the version number.
    Affected if Version displayed is lower than 86.0.4240.75
  3. Determine Chrome version on Linux systems
    Run 'google-chrome --version' in terminal, or on Fedora/Debian/OpenSUSE check via package manager: 'rpm -q google-chrome' or 'dpkg -l google-chrome'.
    Affected if Version returned is below 86.0.4240.75 or package version indicates an unpatched release
  4. Identify if the attack surface applies
    This vulnerability affects Chrome's Intent handling on Android devices. Determine if Chrome for Android is used and whether the device allows installation of third-party apps that could send crafted Intents.
    Affected if Chrome for Android is in use and the device permits third-party app installations or adb-based Intent injection

You are affected if Google Chrome version is below 86.0.4240.75 and you use Chrome for Android where third-party apps or adb access could send malicious Intents.

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

Update Google Chrome on Android to version 86.0.4240.75 or later to patch the Intent policy enforcement vulnerability.

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