dbcve.org
ChromeWeb browser · Google

CVE-2017-15404

HIGH · 7.8 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 61.0.3163.113 or later.
See remediation →
80/100
Remediation priority · High
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
An ability to process crash dumps under root privileges and inappropriate symlinks handling could lead to a local privilege escalation in Crash Reporting in Google Chrome on Chrome OS prior to 61.0.3163.113 allowed a local attacker to perform privilege escalation 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

A local privilege escalation vulnerability existed in Chrome OS Crash Reporting where crash dumps were processed with root privileges and symlinks were handled inappropriately. A crafted HTML page could trigger this to gain elevated privileges.

MitigationUpdate Google Chrome on Chrome OS to version 61.0.3163.113 or later to patch 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:< 61.0.3163.113

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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. Identify the platform
    Determine if the system is running Chrome OS. On Chrome OS, open the terminal (Ctrl+Alt+T) and run 'uname -a' or check if /etc/lsb-release contains 'Chrome OS'. This vulnerability specifically affects Chrome OS Crash Reporting, not regular Chrome on desktop.
    Affected if The system is Chrome OS and the Chrome browser version is below 61.0.3163.113
  2. Check installed Chrome version
    Open Chrome browser, navigate to chrome://version, or go to Settings > About Chrome. Note the full version number displayed (e.g., 61.0.3163.100). Compare this against the affected range of versions before 61.0.3163.113.
    Affected if The displayed version is less than 61.0.3163.113 (e.g., 61.0.3163.100, 60.x, etc.)
  3. Verify crash reporting is accessible
    On Chrome OS, open chrome://crash or check if /proc/mounts contains crashdump or /var/log contains crash reporter paths. The vulnerability requires the crash reporting infrastructure to be present and accessible.
    Affected if Crash reporting paths exist on the system and the browser version is below 61.0.3163.113

You are affected if running Chrome OS with Chrome browser version below 61.0.3163.113 and the crash reporting feature is present on the system.

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 61.0.3163.113 or later
Fixed in 61.0.3163.113
Interim mitigation

Update Google Chrome on Chrome OS to version 61.0.3163.113 or later to patch this vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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