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.

References

• https://nvd.nist.gov/vuln/detail/CVE-2015-5380
• nodejs/node-v0.x-archive#25583
• https://codereview.chromium.org/1226493003
• https://medium.com/@iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
• http://www.securityfocus.com/bid/75556
• 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