dbcve.org
ChromeWeb browser · Google

CVE-2017-5092

HIGH · 8.8 CVSS v3.0 Published 2017-10-27
Fix available
A fix is available. Upgrade to 60.0.3112.78 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Insufficient validation of untrusted input in PPAPI Plugins in Google Chrome prior to 60.0.3112.78 for Windows allowed a remote attacker to potentially perform a sandbox escape 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

Insufficient validation of untrusted input in Google Chrome's PPAPI (Pepper Plugin API) plugin system on Windows allowed remote attackers to inject malicious data through crafted HTML pages. This input validation failure enabled potential sandbox escape, bypassing the browser's critical security boundary.

MitigationUpdate Google Chrome to version 60.0.3112.78 or later on all affected Windows systems to patch the PPAPI input validation 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:< 60.0.3112.78
Debian LinuxOperating system
Affected:= 9.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
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 checks

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

  1. Check Chrome version on Windows
    Open Chrome and navigate to chrome://settings/help, or run 'chrome --version' from the command prompt
    Affected if The displayed version is earlier than 60.0.3112.78
  2. Check Chrome version on Debian Linux
    Run 'dpkg -l | grep -i chrome' or 'apt list --installed | grep -i chrome' in the terminal
    Affected if Chrome is installed and the version is earlier than 60.0.3112.78
  3. Confirm PPAPI plugin usage on Windows
    In Chrome, navigate to chrome://plugins and verify if any PPAPI (Pepper) plugins are enabled and loaded
    Affected if PPAPI plugins are present and enabled on a vulnerable Chrome version

A system is affected if Google Chrome versions prior to 60.0.3112.78 are installed on Windows or Debian Linux with PPAPI plugin functionality active.

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.0.3112.78 or later
Fixed in 60.0.3112.78
Interim mitigation

Update Google Chrome to version 60.0.3112.78 or later on all affected Windows systems to patch the PPAPI input validation vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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