/ 
perl-5.25.4
⭐ Starred 2013
/ valgrindpp.pl
Security Advisories (11)
CVE-2020-12723 (2020-06-05)

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

CVE-2020-10878 (2020-06-05)

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

CVE-2020-10543 (2020-06-05)

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

CVE-2018-18314 (2018-12-07)

Perl before 5.26.3 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

CVE-2018-18313 (2018-12-07)

Perl before 5.26.3 has a buffer over-read via a crafted regular expression that triggers disclosure of sensitive information from process memory.

CVE-2018-18312 (2018-12-05)

Perl before 5.26.3 and 5.28.0 before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

CVE-2018-18311 (2018-12-07)

Perl before 5.26.3 and 5.28.x before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

CVE-2023-47100

In Perl before 5.38.2, S_parse_uniprop_string in regcomp.c can write to unallocated space because a property name associated with a \p{...} regular expression construct is mishandled. The earliest affected version is 5.30.0.

CVE-2024-56406 (2025-04-13)

A heap buffer overflow vulnerability was discovered in Perl. When there are non-ASCII bytes in the left-hand-side of the `tr` operator, `S_do_trans_invmap` can overflow the destination pointer `d`.    $ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;'    Segmentation fault (core dumped) It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.

CVE-2025-40909 (2025-05-30)

Perl threads have a working directory race condition where file operations may target unintended paths. If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running. This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit. The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6

CVE-2023-47039 (2023-10-30)

Perl for Windows relies on the system path environment variable to find the shell (cmd.exe). When running an executable which uses Windows Perl interpreter, Perl attempts to find and execute cmd.exe within the operating system. However, due to path search order issues, Perl initially looks for cmd.exe in the current working directory. An attacker with limited privileges can exploit this behavior by placing cmd.exe in locations with weak permissions, such as C:\ProgramData. By doing so, when an administrator attempts to use this executable from these compromised locations, arbitrary code can be executed.

NAME

valgrindpp.pl - A post processor for make test.valgrind

SYNOPSIS

valgrindpp.pl [--dir=dir] [--frames=number] [--hide=identifier] [--lines] [--output-file=file] [--tests] [--top=number] [--verbose]

DESCRIPTION

valgrindpp.pl is a post processor for .valgrind files created during make test.valgrind. It collects all these files, extracts most of the information and produces a significantly shorter summary of all detected memory access errors and memory leaks.

OPTIONS

--dir=dir

Recursively process .valgrind files in dir. If this options is not given, valgrindpp.pl must be run from either the perl source or the t directory and will process all .valgrind files within the distribution.

--frames=number

Number of stack frames within the perl source code to consider when distinguishing between memory leak sources. Increasing this value will give you a longer backtrace, while decreasing the number will show you fewer sources for memory leaks. The default is 3 frames.

--hide=identifier

Hide all memory leaks that have identifier in their backtrace. Useful if you want to hide leaks from functions that are known to have lots of memory leaks. identifier can also be a regular expression, in which case all leaks with symbols matching the expression are hidden. Can be given multiple times.

--lines

Show line numbers for stack frames. This is useful for further increasing the error/leak resolution, but makes it harder to compare different reports using diff.

--output-file=file

Redirect the output into file. If this option is not given, the output goes to stdout.

--tests

List all tests that trigger memory access errors or memory leaks explicitly instead of only printing a count.

--top=number

List the top number test scripts for memory access errors and memory leaks. Set to 0 for no top-n statistics.

--verbose

Increase verbosity level. Can be given multiple times.

COPYRIGHT

Copyright 2003 by Marcus Holland-Moritz <mhx@cpan.org>.

This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself.