CVE-2016-1669: Buffer overflow in V8

Q: What is the severity of CVE-2016-1669?

CVE-2016-1669 has a severity rating that indicates it can lead to denial of service and potential buffer overflow vulnerabilities.

Q: How do I fix CVE-2016-1669?

To fix CVE-2016-1669, upgrade Google Chrome to version 50.0.2661.10 or later, or update Node.js to the specified remedial versions.

Q: What versions of Google V8 are affected by CVE-2016-1669?

CVE-2016-1669 affects Google V8 versions prior to 5.0.71.

Q: Which software packages are impacted by CVE-2016-1669?

CVE-2016-1669 impacts Google Chrome, multiple versions of Node.js, Debian Linux 8.0, and openSUSE 13.1.

Q: Can CVE-2016-1669 be exploited remotely?

Yes, CVE-2016-1669 can be exploited by remote attackers to cause a denial of service.

Published May 12, 2016

Updated

A buffer overflow flaw was found in the V8 component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=606115

External References:

http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html

Other sources

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.

— MITRE

Under certain conditions, V8 may improperly expand memory allocations in the Zone::New function. This could potentially be used to cause a Denial of Service via buffer overflow or as a trigger for a remote code execution.

Although this bug is marked as high severity in the corresponding Chromium release (50.0.2661.102), our assessment is that this is low severity for Node.js users due to the level of difficulty in making use of this vulnerability. However, users are encouraged to upgrade their Node.js installation to ensure they are properly protected.

— Node.Js

Affected Software

20 affected componentsFixes available

redhat/chrome<50.0.2661.10

50.0.2661.10

redhat/nodejs<0.10.46

0.10.46

redhat/nodejs<0.12.15

0.12.15

redhat/nodejs<4.4.6

4.4.6

redhat/nodejs<5.12.2

5.12.2

redhat/nodejs<6.2.0

6.2.0

Debian Debian Linux=8.0

Google Chrome<=50.0.2661.87

openSUSE openSUSE=13.1

Google V8<=5.0.71

Nodejs Node.js>=0.10.0<0.10.46

Nodejs Node.js>=0.12.0<0.12.15

Nodejs Node.js>=4.0.0<=4.1.2

Nodejs Node.js>=4.2.0<4.4.6

Nodejs Node.js>=5.0.0<5.12.0

Nodejs Node.js>=6.0.0<=6.2.0

Canonical Ubuntu Linux=14.04

Canonical Ubuntu Linux=15.10

Canonical Ubuntu Linux=16.04

Node.js Node.js>=4.0.0<4.4.6, >=5.0.0<5.12.0, >=6.0.0<6.2.0

4.4.65.12.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade redhat/Chrome to a version that resolves this vulnerability.
Fixed in 50.0.2661.10
Upgrade
Upgrade redhat/nodejs to a version that resolves this vulnerability.
Fixed in 0.10.46
Upgrade
Upgrade redhat/nodejs to a version that resolves this vulnerability.
Fixed in 0.12.15
Upgrade
Upgrade redhat/nodejs to a version that resolves this vulnerability.
Fixed in 4.4.6
Upgrade
Upgrade redhat/nodejs to a version that resolves this vulnerability.
Fixed in 5.12.2
Upgrade
Upgrade redhat/nodejs to a version that resolves this vulnerability.
Fixed in 6.2.0
Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.4.6Fixed in 5.12.0
Upgrade
Upgrade Google Chrome to a version that resolves this vulnerability.
Fixed in 50.0.2661.102
Upgrade
Upgrade Google V8 to a version that resolves this vulnerability.
Fixed in 5.0.71.47

Event History

May 14, 2016

CVE Published

via MITRE·09:00 PM

Data Sourced

via MITRE·09:00 PM

Description

Jun 23, 2016

Data Sourced

via Node.js·11:24 PM

Severity

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

What is the severity of CVE-2016-1669?