ChromeWeb browser · Google
CVE-2017-5132
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 · uneditedInappropriate implementation in V8 in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page, aka incorrect WebAssembly stack manipulation.
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 heap corruption vulnerability in Google Chrome's V8 JavaScript engine stems from incorrect WebAssembly stack manipulation. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially allowing arbitrary code execution.
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
< 62.0.3202.62
Debian LinuxOperating system
= 8.0= 9.0CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Google Chrome is installedOn Linux: which google-chrome or dpkg -l | grep chrome. On Windows: Check Program Files for Google Chrome folder or registry. On macOS: ls /Applications | grep -i chromeAffected if Google Chrome browser is present on the system
-
Determine installed Chrome versionRun 'google-chrome --version' on Linux, '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' on Windows, or 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleVersion' on macOSAffected if Installed version is lower than 62.0.3202.62 (e.g., 62.0.3202.61, 61.x.x.x, etc.)
-
Confirm WebAssembly is in useThis vulnerability affects the V8 engine's WebAssembly stack handling. WebAssembly is enabled by default in Chrome. No configuration check needed - any use of WebAssembly in affected versions triggers the condition.Affected if WebAssembly is used or any webpage with WebAssembly content is visited in an affected Chrome version
-
Check Debian package version (if on Debian)Run 'dpkg -l | grep -i chrome' or 'apt-cache policy google-chrome-stable' on Debian 8.0 or 9.0 systemsAffected if Package version is less than 62.0.3202.62-1 or the installed version matches an affected release
The user is affected if Google Chrome version is below 62.0.3202.62 and they browse web pages (including those using WebAssembly) with the vulnerable V8 JavaScript engine.
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 data62.0.3202.62
Update Google Chrome to version 62.0.3202.62 or later to patch the V8 WebAssembly stack manipulation vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5132 — 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-5132 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