# CVE-2015-5380: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution via crafted byte sequences exploiting a memory corruption flaw in the V8 engine.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cpgp-qq89-2x6x

## What is CVE-2015-5380?

CVE-2015-5380 is a high-severity memory corruption vulnerability in Nodejs Node.js, published on 9 Jul 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-5380?

It affects 3 products.


Products: Google V8, Iojs Io.js, Nodejs Node.js.

## How do I fix CVE-2015-5380?

Upgrade to a fixed version.

## Is CVE-2015-5380 being exploited?

There is no known exploitation of CVE-2015-5380 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2011-3886](https://insights.sbomify.com/CVE-2011-3886/): Memory corruption in n/a (medium 6.8)
- [CVE-2011-5037](https://insights.sbomify.com/CVE-2011-5037/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5380 and fix it if it is affected.

What it is: CVE-2015-5380 is a high-severity memory corruption vulnerability in Nodejs Node.js, published on 9 Jul 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5380 in the wild and no public exploit code.

Affected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-5380/ (Markdown: https://insights.sbomify.com/CVE-2015-5380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-5380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-5380
- OSV: https://osv.dev/vulnerability/CVE-2015-5380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-5380/
Summaries are generated and may contain mistakes; the official description above is the record.