dbcve.org
ChromeWeb browser · Google

CVE-2017-15398

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-28
Fix available
A fix is available. Upgrade to 62.0.3202.89 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A stack buffer overflow in the QUIC networking stack in Google Chrome prior to 62.0.3202.89 allowed a remote attacker to gain code execution via a malicious server.

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

Stack buffer overflow in the QUIC networking stack in Google Chrome prior to 62.0.3202.89 allows a remote attacker controlling a malicious server to execute arbitrary code on the client system via crafted QUIC packets.

MitigationUpdate Google Chrome to version 62.0.3202.89 or later to obtain the vendor patch for this vulnerability.

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:< 62.0.3202.89
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Verify Google Chrome is installed
    On Linux: check for /usr/bin/google-chrome or /opt/google/chrome/google-chrome. On Windows: check Program Files/Google/Chrome/Application/chrome.exe. On macOS: check /Applications/Google Chrome.app
    Affected if Google Chrome is not installed on the system
  2. Determine installed Chrome version
    Run 'google-chrome --version' on Linux, 'chrome.exe --version' on Windows, or right-click Google Chrome in macOS Applications > Get Info to see Version
    Affected if The installed version is lower than 62.0.3202.89 (e.g., 62.0.3202.0, 61.x.x.x, etc.)
  3. Check if QUIC protocol is enabled
    Navigate to chrome://flags/#enable-quic in the Chrome browser address bar and inspect the 'Enable QUIC' flag status
    Affected if QUIC is enabled (this is the default setting in affected versions) and the browser connects to remote servers
  4. For Linux distributions (RHEL/Debian)
    Check the packaged Chrome version via package manager: 'rpm -q google-chrome-stable' on RHEL or 'dpkg -l | grep google-chrome' on Debian
    Affected if The system has a bundled Chrome package version below 62.0.3202.89

The user is affected if Google Chrome version is below 62.0.3202.89 and the QUIC protocol feature is enabled (default state), as the vulnerability is triggered by crafted QUIC packets from a malicious server.

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.

dbcve · scoped
Upgrade available Upgrade to 62.0.3202.89 or later
Fixed in 62.0.3202.89
Interim mitigation

Update Google Chrome to version 62.0.3202.89 or later to obtain the vendor patch for this vulnerability.

Recommended fix High confidence

Chrome 62.0.3202.89 or later (preferably latest stable release)

  1. 1. Open Google Chrome on the affected system
  2. 2. Navigate to Chrome menu > Help > About Google Chrome
  3. 3. The browser will automatically check for updates and display the current version
  4. 4. If the version is below 62.0.3202.89, click 'Update Google Chrome'
  5. 5. Restart the browser to apply the update
  6. 6. For Enterprise Linux and Debian systems with system-packaged Chrome, run: sudo yum update google-chrome-stable (RHEL/CentOS) or sudo apt-get update && sudo apt-get upgrade (Debian)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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