# CVE-2014-5256: Denial of service in n/a

> Remote attackers can cause a denial of service via deep JSON objects triggering memory corruption and crashes in Node.js.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 5 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-5256, GHSA-7wxw-9v42-w9g6, UBUNTU-CVE-2014-5256

## What is CVE-2014-5256?

CVE-2014-5256 is a medium-severity denial of service vulnerability in n/a, published on 5 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Node.js 0.8 before 0.8.28 and 0.10 before 0.10.30 does not consider the possibility of recursive processing that triggers V8 garbage collection in conjunction with a V8 interrupt, which allows remote attackers to cause a denial of service (memory corruption and application crash) via deep JSON objects whose parsing lets this interrupt mask an overflow of the program stack.

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

## Which versions are affected by CVE-2014-5256?

It affects 1 product.


Products: Nodejs Nodejs.

## How do I fix CVE-2014-5256?

Upgrade to a fixed version.

## Is CVE-2014-5256 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2330](https://insights.sbomify.com/CVE-2012-2330/): Information disclosure in n/a (medium 6.4)
- [CVE-2013-4450](https://insights.sbomify.com/CVE-2013-4450/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5256 and fix it if it is affected.

What it is: CVE-2014-5256 is a medium-severity denial of service vulnerability in n/a, published on 5 Sep 2014. 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-2014-5256 in the wild and no public exploit code.

Affected product: n/a. 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-2014-5256/ (Markdown: https://insights.sbomify.com/CVE-2014-5256/index.md)
```

## Sources

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

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