dbcve.org
ChromeWeb browser · Google

CVE-2016-5187

MEDIUM · 6.5 CVSS v3.0 Published 2016-12-18
Fix available
A fix is available. Upgrade to after 53.0.2785.143 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
Google Chrome prior to 54.0.2840.85 for Android incorrectly handled rapid transition into and out of full screen mode, which allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via crafted HTML pages.

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

Google Chrome for Android prior to 54.0.2840.85 contained a UI spoofing vulnerability where rapid transitions into and out of fullscreen mode could be exploited to manipulate the Omnibox (URL bar) display. Attackers could craft malicious HTML pages to display misleading URLs, facilitating phishing attacks.

MitigationUpdate Chrome for Android to version 54.0.2840.85 or later on all affected devices.

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:<= 53.0.2785.143

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.0/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. Identify Chrome for Android version
    Open Chrome for Android, tap the three-dot menu, go to Settings, then look for 'Chrome' or 'About Chrome' to view the version number. Alternatively, navigate to chrome://version in the address bar.
    Affected if Version displayed is 53.0.2785.143 or lower (any version up to and including 53.0.2785.143)
  2. Confirm Chrome is the default or commonly used browser
    Check device settings under 'Apps' or 'Default apps' to see if Chrome for Android is set as the default browser or is regularly used for web browsing.
    Affected if Chrome for Android is the default browser or frequently used for browsing on the device
  3. Verify fullscreen API availability
    The vulnerability exploits the fullscreen API in combination with rapid DOM manipulation. No direct config check needed - the flaw exists in the browser's handling of fullscreen transitions regardless of site permissions.
    Affected if Browser has fullscreen API capability (standard in Chrome for Android, enabled by default)

If Chrome for Android version is 53.0.2785.143 or lower, the device is vulnerable to UI spoofing attacks via malicious webpages exploiting rapid fullscreen transitions.

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 a release after 53.0.2785.143
Interim mitigation

Update Chrome for Android to version 54.0.2840.85 or later on all affected devices.

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-2016-5187 — 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-2016-5187 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