ChromeWeb browser · Google
CVE-2017-15406
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 · uneditedA stack buffer overflow in V8 in Google Chrome prior to 62.0.3202.75 allowed a remote attacker to perform an out of bounds memory read 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 stack buffer overflow vulnerability exists in the V8 JavaScript engine in Google Chrome versions prior to 62.0.3202.75. The vulnerability allows a remote attacker to perform out-of-bounds memory reads via a maliciously crafted HTML page, potentially exposing sensitive heap or stack data.
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.75CVSS 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.
-
Check if Google Chrome is installedLook for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or run 'which google-chrome' on Linux)Affected if Google Chrome is not found on the system - the vulnerability does not apply
-
Determine the installed Chrome versionOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' on Linux, or check the executable properties on WindowsAffected if Unable to determine the version - assume potentially vulnerable
-
Compare against vulnerable version rangeCompare the installed version number to 62.0.3202.75 - any version lower than 62.0.3202.75 is in the vulnerable rangeAffected if Installed version is less than 62.0.3202.75 (e.g., 62.0.3202.74, 61.0.3163.100, etc.) - the environment is affected
-
Verify the V8 JavaScript engine is in useThe V8 engine is the default JavaScript engine in Chrome - no additional config check needed; simply having Chrome installed means the V8 engine is presentAffected if Chrome is running with its default JavaScript engine (V8) - the vulnerable component is active
The environment is affected if Google Chrome is installed with a version lower than 62.0.3202.75, as the V8 JavaScript engine stack buffer overflow vulnerability is present in those versions.
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.75
Update Google Chrome to version 62.0.3202.75 or later to patch the V8 stack buffer overflow vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15406 — 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-15406 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