perldelta - what is new for perl v5.36.2
This document describes differences between the 5.36.1 release and the 5.36.2 release.
If you are upgrading from an earlier release such as 5.36.0, first readperl5361delta, which describes differences between 5.36.0 and 5.36.1.
This release fixes the following security issues.
This vulnerability was reported directly to the Perl security team by Nathan Millsthe.true.nathan.mills@gmail.com.
A crafted regular expression when compiled by perl 5.30.0 through 5.38.0 can cause a one-byte attacker controlled buffer overflow in a heap allocated buffer.
This vulnerability was reported to the Intel Product Security Incident Response Team (PSIRT) by GitHub user ycdxsbhttps://github.com/ycdxsb/WindowsPrivilegeEscalation. PSIRT then reported it to the Perl security team.
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 executecmd.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 placingcmd.exe in locations with weak permissions, such asC:\ProgramData. By doing so, when an administrator attempts to use this executable from these compromised locations, arbitrary code can be executed.
Perl 5.36.2 represents approximately 1 month of development since Perl 5.36.1 and contains approximately 2,300 lines of changes across 38 files from 4 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 1,400 lines of changes to 8 .pm, .t, .c and .h files.
Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.36.2:
Karl Williamson, Paul Evans, Steve Hay, Tony Cook.
The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker.
Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish.
For a more complete list of all of Perl's historical contributors, please see theAUTHORS file in the Perl source distribution.
If you find what you think is a bug, you might check the perl bug database athttps://github.com/Perl/perl5/issues. There may also be information athttp://www.perl.org/, the Perl Home Page.
If you believe you have an unreported bug, please open an issue athttps://github.com/Perl/perl5/issues. Be sure to trim your bug down to a tiny but sufficient test case.
If the bug you are reporting has security implications which make it inappropriate to send to a public issue tracker, then see"SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue.
If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running theperlthanks program:
perlthanksThis will send an email to the Perl 5 Porters list with your show of thanks.
TheChanges file for an explanation of how to view exhaustive details on what changed.
TheINSTALL file for how to build Perl.
TheREADME file for general stuff.
TheArtistic andCopying files for copyright information.
Perldoc Browser is maintained by Dan Book (DBOOK). Please contact him via theGitHub issue tracker oremail regarding any issues with the site itself, search, or rendering of documentation.
The Perl documentation is maintained by the Perl 5 Porters in the development of Perl. Please contact them via thePerl issue tracker, themailing list, orIRC to report any issues with the contents or format of the documentation.