Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-4330

perl-Data-Dumper: deep recursion stack overflow

Overview

Published
30 Sep 2014
Modified
6 May 2026
Low CVE
0 Registry packages
5 OS packages
5 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

2.6 · LOW

CVSS 2.0 base score, scored by redhat.

Access vector
Network
Access complexity
High
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:H/Au:N/C:N/I:N/A:P

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
perl-data-dumper
Red Hat fixes for CVE-2014-4330
ReleasePackageFixed in
7 perl-data-dumper +1 wont fix

debian 4 releases · 1 package

fixed 4
perl
debian fixes for CVE-2014-4330
ReleasePackageFixed in
11 perl 5.20.1-1
12 perl 5.20.1-1
13 perl 5.20.1-1
14 perl 5.20.1-1

echo 1 release · 1 package

fixed 1
perl
echo fixes for CVE-2014-4330
ReleasePackageFixed in
perl 5.20.1-1

root.io debian 2 releases · 1 package

fixed 2
rootio-perl
root.io debian fixes for CVE-2014-4330
ReleasePackageFixed in
11 rootio-perl 5.20.1-1
12 rootio-perl 5.20.1-1

seal Red Hat 1 release · 1 package

fixed 1
perl
seal Red Hat fixes for CVE-2014-4330
ReleasePackageFixed in
7 perl +1 4:5.16.3-299.el7_9+sp999

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.