CVE-2015-5380
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,…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (3.00%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 2.0
- 7.5 HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
- EPSS
- 3.00% probability · 87th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-119
- Affected
- google/v8 · iojs/io.js · nodejs/node.js
- Source
- cve@mitre.org
References
- http://blog.nodejs.org/2015/07/03/node-v0-12-6-stable/Patch
- http://www.securityfocus.com/bid/75556
- https://codereview.chromium.org/1226493003
- https://github.com/joyent/node/issues/25583
- https://medium.com/%40iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
- http://blog.nodejs.org/2015/07/03/node-v0-12-6-stable/Patch
- http://www.securityfocus.com/bid/75556
- https://codereview.chromium.org/1226493003
- https://github.com/joyent/node/issues/25583
- https://medium.com/%40iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.