Bug 1139700 (CVE-2014-4330) - CVE-2014-4330 perl-Data-Dumper: deep recursion stack overflow
Summary: CVE-2014-4330 perl-Data-Dumper: deep recursion stack overflow
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2014-4330
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1144903 1144904
Blocks: 1139705
TreeView+ depends on / blocked
 
Reported: 2014-09-09 13:23 UTC by Vasyl Kaigorodov
Modified: 2023-05-12 21:45 UTC (History)
15 users (show)

Fixed In Version: perl-Data-Dumper 2.154
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-14 15:03:54 UTC
Embargoed:


Attachments (Terms of Use)
Upstream provided patch (10.95 KB, patch)
2014-09-09 13:29 UTC, Vasyl Kaigorodov
no flags Details | Diff

Description Vasyl Kaigorodov 2014-09-09 13:23:19 UTC
Upstream reports that they were given a report of stack memory exhaustion
through deep recursion in the Data::Dumper extension.

Original report below:

Issue Description
=================
During internal development a stack overflow was discovered. The cause of the
overflow lies in the Data::Dumper extension which is part of Perl-Core. By using
the "Dumper" method on a large Array-Reference which recursively contains other
Array-References, it is possible to cause many recursive calls to the DD_dump
native function and ultimately exhaust all available stack memory.

Impact
======
When the runtime stack grows over the maximal size, a guard page on most modern
operating systems is hit, causing the Perl interpreter to crash.
Depending on context, code execution might be possible if special circumstances
are met on some architectures.

Temporary Workaround and Fix
============================
Applications written in Perl should make sure that no unnecessary large
array references in terms of recursion are created. On the side of Perl
it should be investigated if the DD_dump function can be implemented
iteratively instead of recursively.

Comment 1 Vasyl Kaigorodov 2014-09-09 13:29:53 UTC
Created attachment 935700 [details]
Upstream provided patch

Attaching upstream patch

Comment 5 Tomas Hoger 2014-09-12 09:35:46 UTC
Upstream bug report (currently not public):

https://rt.perl.org/Public/Bug/Display.html?id=122111

Comment 6 Murray McAllister 2014-09-22 00:25:23 UTC
Acknowledgements:

Red Hat would like to thank the Ricardo Signes for reporting this issue. Upstream acknowledges Markus Vervier of LSE Leading Security Experts as the original reporter.

Comment 8 Murray McAllister 2014-09-22 00:32:21 UTC
Created perl-Data-Dumper tracking bugs for this issue:

Affects: fedora-all [bug 1144903]
Affects: epel-all [bug 1144904]

Comment 9 Jitka Plesnikova 2014-09-22 10:02:50 UTC
Could you please create tracking bugs also for RHEL 7 and RHSCL?

Comment 12 Fedora Update System 2014-09-29 04:06:00 UTC
perl-Data-Dumper-2.154-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2014-10-08 19:17:20 UTC
perl-Data-Dumper-2.154-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Vincent Danen 2014-10-15 20:11:33 UTC
Statement:

This issue affects the versions of perl as shipped with Red Hat Enterprise Linux 6 and the versions of perl-Data-Dumper as shipped with Red Hat Enterprise Linux 7. A future update may address this issue.

Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

Comment 18 Product Security DevOps Team 2021-06-14 15:03:54 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2014-4330


Note You need to log in before you can comment on or make changes to this bug.