dbcve.org
ChromeWeb browser · Google

CVE-2020-6563

MEDIUM · 6.5 CVSS v3.1 Published 2020-09-21
Fix available
A fix is available. Upgrade to 85.0.4183.83 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 intent handling in Google Chrome on Android prior to 85.0.4183.83 allowed a remote attacker to obtain potentially sensitive information from disk 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

Insufficient policy enforcement in Android intent handling in Google Chrome allowed a remote attacker to obtain potentially sensitive information from disk via a crafted HTML page. The vulnerability existed because Chrome did not properly validate or restrict intents (Android's inter-component communication mechanism) before processing them, enabling unauthorized file system access.

MitigationUpdate Google Chrome for Android to version 85.0.4183.83 or later to receive the security patch. Organizations should ensure mobile devices have automatic updates enabled or deploy the update through their MDM solution.

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:< 85.0.4183.83
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 33
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1= 15.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Check Google Chrome for Android version
    Open the Chrome app, tap the three-dot menu, select 'Settings', then tap 'About Chrome' to view the installed version number
    Affected if The displayed version is lower than 85.0.4183.83 (for example, 84.x.x.x or earlier)
  2. Verify Chrome is processing external intents
    This vulnerability is triggered when Chrome processes specially crafted intents from other apps or web pages; no special configuration check is needed as the vulnerable code path is always present in affected versions
    Affected if Chrome version is below 85.0.4183.83 and the browser is used to open external links or content from other apps

A user is affected if Google Chrome for Android version is below 85.0.4183.83 and the browser handles intents from external sources.

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

Update Google Chrome for Android to version 85.0.4183.83 or later to receive the security patch. Organizations should ensure mobile devices have automatic updates enabled or deploy the update through their MDM solution.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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