dbcve.org
ChromeWeb browser · Google

CVE-2017-5008

MEDIUM · 6.1 CVSS v3.0 Published 2017-02-17
Fix available
A fix is available. Upgrade to after 55.0.2883.87 or later.
See remediation →
68/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
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed attacker controlled JavaScript to be run during the invocation of a private script method, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) 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

Universal Cross-Site Scripting (UXSS) vulnerability in Google Chrome's Blink rendering engine. Attackers could run attacker-controlled JavaScript during invocation of a private script method, enabling script or HTML injection into any origin via a crafted HTML page.

MitigationUpgrade Google Chrome to version 56.0.2924.76 or later for desktop platforms, or 56.0.2924.87 or later for Android.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Chrome version in browser
    Open Chrome, click the three-dot menu > Settings, then click 'About Chrome' at the bottom of the left panel, or navigate directly to chrome://settings/help
    Affected if The displayed version number is 55.0.2883.87 or lower (e.g., 55.0.2883.75)
  2. Check Chrome version via command line
    Run 'google-chrome --version' on Linux, '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' on macOS, or check the registry key 'HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon\version' on Windows
    Affected if The reported version is 55.0.2883.87 or lower
  3. Confirm the Blink engine is active
    This vulnerability affects the Blink rendering engine which is used by Chrome. Open any webpage and inspect the user agent string or navigate to chrome://version to verify Blink is in use
    Affected if The rendering engine listed is Blink and the Chrome version meets the affected criteria above

You are affected if Google Chrome is installed and its version is 55.0.2883.87 or lower, since this version uses the vulnerable Blink rendering engine.

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 55.0.2883.87
Interim mitigation

Upgrade Google Chrome to version 56.0.2924.76 or later for desktop platforms, or 56.0.2924.87 or later for Android.

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-2017-5008 — 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-2017-5008 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