PERL5263DELTA(1) Perl Programmers Reference Guide PERL5263DELTA(1) #
PERL5263DELTA(1) Perl Programmers Reference Guide PERL5263DELTA(1)
NNAAMMEE #
perl5263delta - what is new for perl v5.26.3
DDEESSCCRRIIPPTTIIOONN #
This document describes differences between the 5.26.2 release and the
5.26.3 release.
If you are upgrading from an earlier release such as 5.26.1, first read
perl5262delta, which describes differences between 5.26.1 and 5.26.2.
SSeeccuurriittyy [[CCVVEE--22001188--1122001155]] DDiirreeccttoorryy ttrraavveerrssaall iinn mmoodduullee AArrcchhiivvee::::TTaarr By default, Archive::Tar doesn’t allow extracting files outside the current working directory. However, this secure extraction mode could be bypassed by putting a symlink and a regular file with the same name into the tar file.
[GH #16580] <https://github.com/Perl/perl5/issues/16580> [cpan #125523]
<https://rt.cpan.org/Ticket/Display.html?id=125523>
[[CCVVEE--22001188--1188331111]] IInntteeggeerr oovveerrffllooww lleeaaddiinngg ttoo bbuuffffeerr oovveerrffllooww aanndd sseeggmmeennttaattiioonn ffaauulltt Integer arithmetic in “Perl_my_setenv()” could wrap when the combined length of the environment variable name and value exceeded around 0x7fffffff. This could lead to writing beyond the end of an allocated buffer with attacker supplied data.
[GH #16560] <https://github.com/Perl/perl5/issues/16560>
[[CCVVEE--22001188--1188331122]] HHeeaapp--bbuuffffeerr--oovveerrffllooww wwrriittee iinn SS__rreeggaattoomm ((rreeggccoommpp..cc)) A crafted regular expression could cause heap-buffer-overflow write during compilation, potentially allowing arbitrary code execution.
[GH #16649] <https://github.com/Perl/perl5/issues/16649>
[[CCVVEE--22001188--1188331133]] HHeeaapp--bbuuffffeerr--oovveerrffllooww rreeaadd iinn SS__ggrrookk__bbssllaasshh__NN ((rreeggccoommpp..cc)) A crafted regular expression could cause heap-buffer-overflow read during compilation, potentially leading to sensitive information being leaked.
[GH #16554] <https://github.com/Perl/perl5/issues/16554>
[[CCVVEE--22001188--1188331144]] HHeeaapp--bbuuffffeerr--oovveerrffllooww wwrriittee iinn SS__rreeggaattoomm ((rreeggccoommpp..cc)) A crafted regular expression could cause heap-buffer-overflow write during compilation, potentially allowing arbitrary code execution.
[GH #16041] <https://github.com/Perl/perl5/issues/16041>
IInnccoommppaattiibbllee CChhaannggeess There are no changes intentionally incompatible with 5.26.2. If any exist, they are bugs, and we request that you submit a report. See “Reporting Bugs” below.
MMoodduulleess aanndd PPrraaggmmaattaa UUppddaatteedd MMoodduulleess aanndd PPrraaggmmaattaa • Archive::Tar has been upgraded from version 2.24 to 2.24_01.
• Module::CoreList has been upgraded from version 5.20180414_26 to
5.20181129_26.
DDiiaaggnnoossttiiccss The following additions or changes have been made to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, see perldiag.
NNeeww DDiiaaggnnoossttiiccss _N_e_w _E_r_r_o_r_s
• Unexpected ']' with no following ')' in (?[... in regex; marked by
<-- HERE in m/%s/
(F) While parsing an extended character class a ']' character was
encountered at a point in the definition where the only legal use of
']' is to close the character class definition as part of a '])', you
may have forgotten the close paren, or otherwise confused the parser.
• Expecting close paren for nested extended charclass in regex; marked
by <-- HERE in m/%s/
(F) While parsing a nested extended character class like:
(?[ ... (?flags:(?[ ... ])) ... ])
^
we expected to see a close paren ')' (marked by ^) but did not.
• Expecting close paren for wrapper for nested extended charclass in
regex; marked by <-- HERE in m/%s/
(F) While parsing a nested extended character class like:
(?[ ... (?flags:(?[ ... ])) ... ])
^
we expected to see a close paren ')' (marked by ^) but did not.
CChhaannggeess ttoo EExxiissttiinngg DDiiaaggnnoossttiiccss • Syntax error in (?[…]) in regex; marked by <– HERE in m/%s/
This fatal error message has been slightly expanded (from "Syntax
error in (?[...]) in regex m/%s/") for greater clarity.
AAcckknnoowwlleeddggeemmeennttss Perl 5.26.3 represents approximately 8 months of development since Perl 5.26.2 and contains approximately 4,500 lines of changes across 51 files from 15 authors.
Excluding auto-generated files, documentation and release tools, there
were approximately 770 lines of changes to 10 .pm, .t, .c and .h files.
Perl continues to flourish into its third decade thanks to a vibrant
community of users and developers. The following people are known to
have contributed the improvements that became Perl 5.26.3:
Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari Mannsåker,
David Mitchell, H.Merijn Brand, James E Keenan, John SJ Anderson, Karen
Etheridge, Karl Williamson, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook,
Yves Orton.
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 the _A_U_T_H_O_R_S file in the Perl source distribution.
RReeppoorrttiinngg BBuuggss If you find what you think is a bug, you might check the perl bug database at https://rt.perl.org/ . There may also be information at http://www.perl.org/ , the Perl Home Page.
If you believe you have an unreported bug, please run the perlbug program
included with your release. Be sure to trim your bug down to a tiny but
sufficient test case. Your bug report, along with the output of "perl
-V", will be sent off to perlbug@perl.org to be analysed by the Perl
porting team.
If the bug you are reporting has security implications which make it
inappropriate to send to a publicly archived mailing list, then see
"SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of
how to report the issue.
GGiivvee TThhaannkkss If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the “perlthanks” program:
perlthanks
This will send an email to the Perl 5 Porters list with your show of
thanks.
SSEEEE AALLSSOO #
The _C_h_a_n_g_e_s file for an explanation of how to view exhaustive details on
what changed.
The _I_N_S_T_A_L_L file for how to build Perl.
The _R_E_A_D_M_E file for general stuff.
The _A_r_t_i_s_t_i_c and _C_o_p_y_i_n_g files for copyright information.
perl v5.36.3 2023-02-15 PERL5263DELTA(1)