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

> Attackers can cause a denial of service via stack consumption in the Data::Dumper Perl module by submitting deeply nested array references.

- **Severity:** Low 2.1 (`AV:L/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:** 30 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-4330, GHSA-gxvp-m937-jg9v, MGASA-2014-0405, MGASA-2014-0406, MGASA-2014-0407, SUSE-RU-2015:0562-1, UBUNTU-CVE-2014-4330

## What is CVE-2014-4330?

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

### Official description

The Dumper method in Data::Dumper before 2.154, as used in Perl 5.20.1 and earlier, allows context-dependent attackers to cause a denial of service (stack consumption and crash) via an Array-Reference with many nested Array-References, which triggers a large number of recursive calls to the DD_dump function.

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

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

It affects 2 products.


Products: Data Dumper Project Data Dumper, Perl Perl.

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

Upgrade to a fixed version.

## Is CVE-2014-4330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-4330 is a low-severity denial of service vulnerability in n/a, published on 30 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-4330 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-4330/ (Markdown: https://insights.sbomify.com/CVE-2014-4330/index.md)
```

## Sources

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

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