ChromeWeb browser · Google
CVE-2017-5010
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 · uneditedBlink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, resolved promises in an inappropriate context, 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 confidenceA Universal Cross-Site Scripting (UXSS) vulnerability in Google Chrome's Blink rendering engine where promises were resolved in an inappropriate context. This allowed a remote attacker to inject arbitrary scripts or HTML via a crafted HTML page.
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
<= 55.0.2883.87CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedOn Windows: Check for chrome.exe in Program Files or AppData\Local\Google\Chrome\Application\. On macOS: Check /Applications/Google Chrome.app. On Linux: Check /opt/google/chrome or via package manager.Affected if Google Chrome browser is present on the system
-
Retrieve the installed Chrome version numberOpen chrome://version in the Chrome address bar and note the version string, or run 'google-chrome --version' on Linux, or 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows via command prompt.Affected if Unable to determine the version indicates Chrome may be installed but version cannot be verified
-
Compare installed version against affected rangeParse the version number (e.g., 55.0.2883.87). The vulnerability affects versions up to and including 55.0.2883.87. If your version is 55.0.2883.87 or lower, it falls within the affected range.Affected if Installed version is 55.0.2883.87 or any earlier version (e.g., 54.x.x.x, 53.x.x.x)
-
Verify Blink rendering engine contextThis vulnerability specifically requires the Blink rendering engine to resolve promises in an inappropriate security context. The vulnerability is present in any Chrome version <= 55.0.2883.87 that uses the Blink engine.Affected if Chrome version is <= 55.0.2883.87 and the Blink rendering engine is active (default for this version range)
If the installed Google Chrome version is 55.0.2883.87 or any earlier version, the environment is vulnerable to this UXSS flaw via Blink promise resolution.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate 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
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5010 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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