CVE-2015-5380
Published: 9 July 2015
The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.x before 2.3.3, and other products, does not verify that there is memory available for a UTF-16 surrogate pair, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted byte sequence.
Notes
Author | Note |
---|---|
msalvatore | Does not affect Node.js before 0.12.0 |
Priority
Status
Package | Release | Status |
---|---|---|
nodejs Launchpad, Ubuntu, Debian |
artful |
Ignored
(end of life)
|
bionic |
Not vulnerable
(8.10.0~dfsg-2)
|
|
precise |
Ignored
(end of life)
|
|
trusty |
Not vulnerable
(code not present)
|
|
upstream |
Not vulnerable
(code not present)
|
|
utopic |
Ignored
(end of life)
|
|
vivid |
Ignored
(end of life)
|
|
wily |
Ignored
(end of life)
|
|
xenial |
Not vulnerable
(4.2.6~dfsg-1ubuntu4.1)
|
|
yakkety |
Ignored
(end of life)
|
|
zesty |
Ignored
(end of life)
|
References
- http://www.openwall.com/lists/oss-security/2015/07/05/1
- https://medium.com/@iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
- http://blog.nodejs.org/2015/07/03/node-v0-12-6-stable/
- https://github.com/joyent/node/issues/25583
- https://codereview.chromium.org/1226493003
- https://www.cve.org/CVERecord?id=CVE-2015-5380
- NVD
- Launchpad
- Debian