ChromeWeb browser · Google
CVE-2017-15396
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 NumberingSystem in International Components for Unicode (ICU) for C/C++ before 60.2, as used in V8 in Google Chrome prior to 62.0.3202.75 and other products, allowed a remote attacker to potentially exploit heap corruption 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 NumberingSystem component of the International Components for Unicode (ICU) library for C/C++ before version 60.2. The flaw is exposed through V8 JavaScript engine in Google Chrome and allows a remote attacker to trigger the overflow via a crafted HTML page, potentially leading to heap corruption.
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.75
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 8.0= 9.0= 10.0< 60.2CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 ICU library versionRun 'icuinfo' or 'pkg-config --modversion icu-i18n' to retrieve the installed ICU version, or inspect the shared library file (e.g., libicuuc.so) using 'ldd' or 'file' to identify the version embedded in the filenameAffected if The ICU version is less than 60.2
-
Check Google Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from the command lineAffected if Chrome version is less than 62.0.3202.75
-
Identify applications using ICU NumberingSystemSearch application logs or code for calls to ICU APIs involving NumberingSystem (e.g., unum_open with UNumberFormatSymbol or NumberFormat::createInstance), or inspect which applications dynamically link to libicuucAffected if Any application uses ICU's NumberingSystem functionality with a vulnerable ICU version
-
Check ICU development headers if compiling from sourceInspect the icu/common/unumber.h header file or the icu/source/common/unicode/uversion.h file to confirm the version number embedded in the sourceAffected if The header defines a version lower than 60.2
You are affected if ICU library version is below 60.2 OR Chrome browser version is below 62.0.3202.75, AND the NumberingSystem component is actively used by your applications.
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 data60.262.0.3202.75
Update ICU library to version 60.2 or later, and update Google Chrome to version 62.0.3202.75 or later. For other products using the affected ICU versions, apply vendor-specific patches and verify all dependent components.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15396 — 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-15396 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