dbcve.org
ChromeWeb browser · Google

CVE-2020-6487

MEDIUM · 6.5 CVSS v3.1 Published 2020-05-21
Fix available
A fix is available. Upgrade to 83.0.4103.61 or later.
See remediation →
72/100
Remediation priority · Elevated
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 downloads in Google Chrome prior to 83.0.4103.61 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

Insufficient policy enforcement in Google Chrome's downloads component prior to version 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions by tricking users into opening a crafted HTML page, potentially leading to unauthorized downloads or navigation to malicious sites.

MitigationUpgrade Google Chrome to version 83.0.4103.61 or later. No network-level mitigation is available since this is a client-side browser 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:< 83.0.4103.61
Debian LinuxOperating system
Affected:= 9.0= 10.0
FedoraOperating system
Affected:= 31= 32
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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. Confirm Google Chrome is installed
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' in terminal. On systems with Chromium only, run 'chromium --version' or 'chromium-browser --version'.
    Affected if Google Chrome or Chromium browser is present on the system
  2. Identify the exact Chrome version number
    Locate the version string displayed in chrome://version (e.g., 83.0.4103.60) or the output of the version command. Record the full version including build number.
    Affected if The full version number cannot be determined or the browser is unversioned
  3. Compare version against affected range
    Compare your installed version to the affected threshold: versions prior to 83.0.4103.61 are vulnerable. For example, 83.0.4103.60 is affected, while 83.0.4103.61 and later are not.
    Affected if Installed version is less than 83.0.4103.61 (e.g., 83.0.4103.60, 83.0.4103.0, 82.x.x.x, etc.)
  4. Check OS-distributed Chrome packages (Linux)
    On Debian-based systems: 'dpkg -l | grep chrome' or 'apt show google-chrome-stable'. On Fedora: 'rpm -qa | grep chrome'. On openSUSE: 'rpm -qa | grep chrome'. These show the packaged version shipped by the distribution.
    Affected if The OS package version is listed as vulnerable per the affected distribution versions (Debian 9/10, Fedora 31/32, openSUSE 15.0/15.1)
  5. Verify Downloads component accessibility
    While this is the attack surface rather than a detection method, confirm the Downloads feature is accessible in the browser. The vulnerability allows bypassing navigation restrictions when users are tricked into opening crafted HTML pages that trigger unauthorized downloads.
    Affected if Downloads component is enabled and accessible (default state)

The environment is affected if Google Chrome or Chromium is installed with a version lower than 83.0.4103.61, or if the OS-distributed Chrome package matches the affected Debian/Fedora/openSUSE versions.

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

Upgrade Google Chrome to version 83.0.4103.61 or later. No network-level mitigation is available since this is a client-side browser vulnerability.

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