dbcve.org
ChromeWeb browser · Google

CVE-2016-5172

MEDIUM · 6.5 CVSS v3.1 Published 2016-09-25
Fix available
A fix is available. Upgrade to after 53.0.2785.101 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
The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory locations via crafted JavaScript code.

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

The V8 JavaScript engine parser in Google Chrome before 53.0.2785.113 contains a scope handling flaw that allows crafted JavaScript code to read arbitrary memory locations, enabling remote attackers to potentially obtain sensitive information from the process memory space.

MitigationUpgrade Google Chrome to version 53.0.2785.113 or later to patch the V8 parser scope handling 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:<= 53.0.2785.101
Node.jsApplication
Affected:>= 6.0.0, <= 6.8.1
Debian LinuxOperating system
Affected:= 8.0= 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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://version in the browser address bar or run 'google-chrome --version' from command line
    Affected if Version is 53.0.2785.101 or lower
  2. Check Node.js version
    Run 'node --version' in terminal
    Affected if Version is 6.0.0 through 6.8.1 inclusive
  3. Check embedded V8 version in Node.js
    Run 'node -p process.versions.v8' to display the V8 engine version
    Affected if V8 version corresponds to the affected Node.js range (typically 5.1.x through 5.1.281.93 or similar within 6.0-6.8.1)
  4. Check if running Debian 8 or 9 with packaged Chromium
    Run 'cat /etc/debian_version' and 'apt-cache policy chromium' or 'apt-cache policy chromium-browser'
    Affected if Debian version is 8.0 or 9.0 and the installed Chromium package version matches the vulnerable Chrome range

You are affected if you run Google Chrome 53.0.2785.101 or lower, or Node.js 6.0.0 through 6.8.1, or Debian 8.0/9.0 with a vulnerable Chromium/Node.js package installed.

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 a release after 53.0.2785.101
Interim mitigation

Upgrade Google Chrome to version 53.0.2785.113 or later to patch the V8 parser scope handling vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2016-5172 — 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-2016-5172 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