1=encoding utf8 2 3=head1 NAME 4 5perl5263delta - what is new for perl v5.26.3 6 7=head1 DESCRIPTION 8 9This document describes differences between the 5.26.2 release and the 5.26.3 10release. 11 12If you are upgrading from an earlier release such as 5.26.1, first read 13L<perl5262delta>, which describes differences between 5.26.1 and 5.26.2. 14 15=head1 Security 16 17=head2 [CVE-2018-12015] Directory traversal in module Archive::Tar 18 19By default, L<Archive::Tar> doesn't allow extracting files outside the current 20working directory. However, this secure extraction mode could be bypassed by 21putting a symlink and a regular file with the same name into the tar file. 22 23L<[GH #16580]|https://github.com/Perl/perl5/issues/16580> 24L<[cpan #125523]|https://rt.cpan.org/Ticket/Display.html?id=125523> 25 26=head2 [CVE-2018-18311] Integer overflow leading to buffer overflow and segmentation fault 27 28Integer arithmetic in C<Perl_my_setenv()> could wrap when the combined length 29of the environment variable name and value exceeded around 0x7fffffff. This 30could lead to writing beyond the end of an allocated buffer with attacker 31supplied data. 32 33L<[GH #16560]|https://github.com/Perl/perl5/issues/16560> 34 35=head2 [CVE-2018-18312] Heap-buffer-overflow write in S_regatom (regcomp.c) 36 37A crafted regular expression could cause heap-buffer-overflow write during 38compilation, potentially allowing arbitrary code execution. 39 40L<[GH #16649]|https://github.com/Perl/perl5/issues/16649> 41 42=head2 [CVE-2018-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c) 43 44A crafted regular expression could cause heap-buffer-overflow read during 45compilation, potentially leading to sensitive information being leaked. 46 47L<[GH #16554]|https://github.com/Perl/perl5/issues/16554> 48 49=head2 [CVE-2018-18314] Heap-buffer-overflow write in S_regatom (regcomp.c) 50 51A crafted regular expression could cause heap-buffer-overflow write during 52compilation, potentially allowing arbitrary code execution. 53 54L<[GH #16041]|https://github.com/Perl/perl5/issues/16041> 55 56=head1 Incompatible Changes 57 58There are no changes intentionally incompatible with 5.26.2. If any exist, 59they are bugs, and we request that you submit a report. See 60L</Reporting Bugs> below. 61 62=head1 Modules and Pragmata 63 64=head2 Updated Modules and Pragmata 65 66=over 4 67 68=item * 69 70L<Archive::Tar> has been upgraded from version 2.24 to 2.24_01. 71 72=item * 73 74L<Module::CoreList> has been upgraded from version 5.20180414_26 to 5.20181129_26. 75 76=back 77 78=head1 Diagnostics 79 80The following additions or changes have been made to diagnostic output, 81including warnings and fatal error messages. For the complete list of 82diagnostic messages, see L<perldiag>. 83 84=head2 New Diagnostics 85 86=head3 New Errors 87 88=over 4 89 90=item * 91 92L<Unexpected ']' with no following ')' in (?[... in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>|perldiag/"Unexpected ']' with no following ')' in (?[... in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>"> 93 94(F) While parsing an extended character class a ']' character was encountered 95at a point in the definition where the only legal use of ']' is to close the 96character class definition as part of a '])', you may have forgotten the close 97paren, or otherwise confused the parser. 98 99=item * 100 101L<Expecting close paren for nested extended charclass in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>|perldiag/"Expecting close paren for nested extended charclass in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>"> 102 103(F) While parsing a nested extended character class like: 104 105 (?[ ... (?flags:(?[ ... ])) ... ]) 106 ^ 107 108we expected to see a close paren ')' (marked by ^) but did not. 109 110=item * 111 112L<Expecting close paren for wrapper for nested extended charclass in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>|perldiag/"Expecting close paren for wrapper for nested extended charclass in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>"> 113 114(F) While parsing a nested extended character class like: 115 116 (?[ ... (?flags:(?[ ... ])) ... ]) 117 ^ 118 119we expected to see a close paren ')' (marked by ^) but did not. 120 121=back 122 123=head2 Changes to Existing Diagnostics 124 125=over 4 126 127=item * 128 129L<Syntax error in (?[...]) in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>|perldiag/"Syntax error in (?[...]) in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>"> 130 131This fatal error message has been slightly expanded (from "Syntax error in 132(?[...]) in regex mE<sol>%sE<sol>") for greater clarity. 133 134=back 135 136=head1 Acknowledgements 137 138Perl 5.26.3 represents approximately 8 months of development since Perl 5.26.2 139and contains approximately 4,500 lines of changes across 51 files from 15 140authors. 141 142Excluding auto-generated files, documentation and release tools, there were 143approximately 770 lines of changes to 10 .pm, .t, .c and .h files. 144 145Perl continues to flourish into its third decade thanks to a vibrant community 146of users and developers. The following people are known to have contributed 147the improvements that became Perl 5.26.3: 148 149Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari Mannsåker, David 150Mitchell, H.Merijn Brand, James E Keenan, John SJ Anderson, Karen Etheridge, 151Karl Williamson, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook, Yves Orton. 152 153The list above is almost certainly incomplete as it is automatically generated 154from version control history. In particular, it does not include the names of 155the (very much appreciated) contributors who reported issues to the Perl bug 156tracker. 157 158Many of the changes included in this version originated in the CPAN modules 159included in Perl's core. We're grateful to the entire CPAN community for 160helping Perl to flourish. 161 162For a more complete list of all of Perl's historical contributors, please see 163the F<AUTHORS> file in the Perl source distribution. 164 165=head1 Reporting Bugs 166 167If you find what you think is a bug, you might check the perl bug database 168at L<https://rt.perl.org/> . There may also be information at 169L<http://www.perl.org/> , the Perl Home Page. 170 171If you believe you have an unreported bug, please run the L<perlbug> program 172included with your release. Be sure to trim your bug down to a tiny but 173sufficient test case. Your bug report, along with the output of C<perl -V>, 174will be sent off to perlbug@perl.org to be analysed by the Perl porting team. 175 176If the bug you are reporting has security implications which make it 177inappropriate to send to a publicly archived mailing list, then see 178L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> 179for details of how to report the issue. 180 181=head1 Give Thanks 182 183If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, 184you can do so by running the C<perlthanks> program: 185 186 perlthanks 187 188This will send an email to the Perl 5 Porters list with your show of thanks. 189 190=head1 SEE ALSO 191 192The F<Changes> file for an explanation of how to view exhaustive details on 193what changed. 194 195The F<INSTALL> file for how to build Perl. 196 197The F<README> file for general stuff. 198 199The F<Artistic> and F<Copying> files for copyright information. 200 201=cut 202