Security Advisories (8)
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-6798 (2018-04-17)

An issue was discovered in Perl 5.22 through 5.26. Matching a crafted locale dependent regular expression can cause a heap-based buffer over-read and potentially information disclosure.

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.

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

NAME

git-deltatool - Annotate commits for perldelta

SYNOPSIS

# annotate commits back to last 'git describe' tag

$ git-deltatool

# review annotations

$ git-deltatool --mode review

# review commits needing help

$ git-deltatool --mode review --type blocking

# summarize commits needing help

$ git-deltatool --mode summary --type blocking

# assemble annotations by section to STDOUT

$ git-deltatool --mode render

# Get a list of commits needing further review, e.g. for peer review

$ git-deltatool --mode summary --type blocking

# mark 'pending' annotations as 'done' (i.e. added to perldelta)

$ git-deltatool --mode update --type pending --status done

OPTIONS

--mode|-m MODE

Indicates the run mode for the program. The default is 'assign' which assigns categories and marks the notes as 'pending' (or 'ignored'). Other modes are 'review', 'render', 'summary' and 'update'.

--type|-t TYPE

Indicates what types of commits to process. The default for 'assign' mode is 'new', which processes commits without any perldelta notes. The default for 'review', 'summary' and 'render' modes is 'pending'. The options must be set explicitly for 'update' mode.

The type 'blocking' is reserved for commits needing further review.

--status|-s STATUS

For 'update' mode only, sets a new status. While there is no restriction, it should be one of 'new', 'pending', 'blocking', 'ignored' or 'done'.

--since REVISION

Defines the boundary for searching git commits. Defaults to the last major tag (as would be given by 'git describe').

--help

Shows the manual.

TODO

It would be nice to make some of the structured sections smarter -- e.g. look at changed files in pod/* for Documentation section entries. Likewise it would be nice to collate them during the render phase -- e.g. cluster all platform-specific things properly.

AUTHOR

David Golden <dagolden@cpan.org>

COPYRIGHT AND LICENSE

This software is copyright (c) 2010 by David Golden.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.