dbcve.org
ChromeWeb browser · Google

CVE-2017-15422

MEDIUM · 6.5 CVSS v3.0 Published 2018-08-28
Fix available
A fix is available. Upgrade to 60.1 / 63.0.3239.84 or later.
See remediation →
72/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
Integer overflow in international date handling in International Components for Unicode (ICU) for C/C++ before 60.1, as used in V8 in Google Chrome prior to 63.0.3239.84 and other products, 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 confidence

Integer overflow in the international date handling functions of the International Components for Unicode (ICU) library for C/C++ before version 60.1, as used in V8 JavaScript engine in Google Chrome prior to 63.0.3239.84, allows a remote attacker to perform an out-of-bounds memory read via a crafted HTML page.

MitigationUpdate ICU library to version 60.1 or later in all affected software, and update Google Chrome to version 63.0.3239.84 or later to incorporate the fixed ICU version.

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:< 63.0.3239.84
Debian LinuxOperating system
Affected:= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
International Components For UnicodeApplication
Affected:< 60.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version
    Open Chrome, go to Menu > Help > About Google Chrome, or navigate to chrome://version to see the installed version number
    Affected if The version displayed is earlier than 63.0.3239.84
  2. Check ICU library version on Linux
    Run 'icuinfo' or check the ICU version file typically found in /usr/share/icu or via package manager: dpkg -l | grep icu or rpm -qa | grep icu
    Affected if The ICU version is earlier than 60.1 (such as 59.x, 58.x, or older)
  3. Verify if Debian system has vulnerable packages
    Run 'dpkg -l | grep -E "(chromium|icu)"' to list installed packages, then check version numbers against affected Debian versions 8.0 and 9.0
    Affected if Chromium or ICU packages from Debian 8.0 or 9.0 are installed without security updates
  4. Verify if Ubuntu system has vulnerable packages
    Run 'dpkg -l | grep -E "(chromium|icu)"' or check Software Center for installed versions, comparing against Ubuntu 14.04, 16.04, or 17.10
    Affected if Chromium or ICU packages from the listed Ubuntu versions are installed without updates
  5. Verify if RHEL/CentOS system has vulnerable packages
    Run 'rpm -qa | grep -E "(chrome|icu)"' to list installed packages, checking version against RHEL 6.0 baseline
    Affected if Chrome or ICU packages from RHEL 6.0 are installed without later updates

You are affected if you are running Google Chrome before 63.0.3239.84, or any ICU library version earlier than 60.1, particularly on the listed Debian, Ubuntu, or RHEL versions.

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 60.1 / 63.0.3239.84 or later
Fixed in 60.163.0.3239.84
Interim mitigation

Update ICU library to version 60.1 or later in all affected software, and update Google Chrome to version 63.0.3239.84 or later to incorporate the fixed ICU version.

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15422 — 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-15422 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