/ 
perl-5.34.0-RC2
⭐ Starred 2013
/ t/comp/opsubs.t
Security Advisories (6)
CVE-2022-48522 (2023-08-22)

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

CVE-2023-47038 (2023-10-30)

A crafted regular expression when compiled by perl 5.30.0 through 5.38.0 can cause a one attacker controlled byte buffer overflow in a heap allocated buffer

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

A heap buffer overflow vulnerability was discovered in Perl. Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10. 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.

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.

Even if you have a sub q{}, calling q() will be parsed as the q() operator. Calling &q() or main::q() gets you the function. This test verifies this behavior for nine different operators.

from irc://irc.perl.org/p5p 2004/08/12

<kane-xs>  bug or feature?
<purl>     You decide!!!!
<kane-xs>  [kane@coke ~]$ perlc -le'sub y{1};y(1)'
<kane-xs>  Transliteration replacement not terminated at -e line 1.
<Nicholas> bug I think
<kane-xs>  i'll perlbug
<rgs>      feature
<kane-xs>  smiles at rgs
<kane-xs>  done
<rgs>      will be closed at not a bug,
<rgs>      like the previous reports of this one
<Nicholas> feature being first class and second class keywords?
<rgs>      you have similar ones with q, qq, qr, qx, tr, s and m
<rgs>      one could say 1st class keywords, yes
<rgs>      and I forgot qw
<kane-xs>  hmm silly...
<Nicholas> it's acutally operators, isn't it?
<Nicholas> as in you can't call a subroutine with the same name as an
           operator unless you have the & ?
<kane-xs>  or fqpn (fully qualified package name)
<kane-xs>  main::y() works just fine
<kane-xs>  as does &y; but not y()
<Andy>     If that's a feature, then let's write a test that it continues
           to work like that.