dbcve.org
Debian LinuxOperating system · Debian

CVE-2016-1669

HIGH · 8.8 CVSS v3.1 Published 2016-05-14
Fix available
A fix is available. Upgrade to 0.10.46 / 0.12.15 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
The Zone::New function in zone.cc in Google V8 before 5.0.71.47, as used in Google Chrome before 50.0.2661.102, does not properly determine when to expand certain memory allocations, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact 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

A buffer overflow vulnerability exists in the Zone::New function in zone.cc of Google V8 JavaScript engine (versions prior to 5.0.71.47). The function fails to properly validate when to expand memory allocations, allowing crafted JavaScript code to overflow buffers. This vulnerability is present in Google Chrome versions before 50.0.2661.102 and can be exploited remotely via malicious JavaScript execution.

MitigationUpdate Google Chrome to version 50.0.2661.102 or later, or update the V8 JavaScript engine to version 5.0.71.47 or later in any product that embeds it.

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
Debian LinuxOperating system
Affected:= 8.0
ChromeWeb browser
Affected:<= 50.0.2661.87
Node.jsApplication
Affected:>= 0.10.0, < 0.10.46>= 0.12.0, < 0.12.15>= 4.0.0, <= 4.1.2>= 4.2.0, < 4.4.6>= 5.0.0, < 5.12.0>= 6.0.0, <= 6.2.0
Ubuntu LinuxOperating system
Affected:= 14.04= 15.10= 16.04
OpensuseOperating system
Affected:= 13.1
V8Application
Affected:<= 5.0.71

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.1/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. Identify if Google Chrome is installed
    Open Chrome, go to Menu > Help > About Google Chrome, or navigate to chrome://version/ to see the installed version number
    Affected if Chrome version is 50.0.2661.87 or lower (any version below 50.0.2661.102)
  2. Identify if Node.js is installed
    Run 'node --version' in a terminal to get the Node.js version, and run 'node -p process.versions.v8' to get the V8 version bundled with it
    Affected if Node.js version is 0.10.0 to 0.10.45, 0.12.0 to 0.12.14, 4.0.0 to 4.1.2, 4.2.0 to 4.4.5, 5.0.0 to 5.11.0, or 6.0.0 to 6.2.0 (any version within the affected ranges)
  3. Identify if V8 engine is embedded in another product
    Check the product documentation or run 'v8 --version' if V8 is accessible as a standalone component
    Affected if V8 version is 5.0.71 or lower (any version prior to 5.0.71.47)
  4. Check Linux system packages for vulnerable Chrome or V8
    On Debian/Ubuntu run 'dpkg -l | grep -i chrome' or 'dpkg -l | grep -i v8'; on OpenSUSE run 'rpm -qa | grep -i v8'
    Affected if Installed package version matches the affected version ranges for the respective distribution

You are affected if your Chrome is 50.0.2661.87 or lower, your Node.js falls within any of the listed affected version ranges, or your V8 version is 5.0.71 or lower.

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 0.10.46 / 0.12.15 / 4.4.6 or later
Fixed in 0.10.460.12.154.4.6
Interim mitigation

Update Google Chrome to version 50.0.2661.102 or later, or update the V8 JavaScript engine to version 5.0.71.47 or later in any product that embeds it.

Fix this in Debian Linux 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-1669 — 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-1669 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