name : perl5244delta.pod =encoding utf8 =head1 NAME perl5244delta - what is new for perl v5.24.4 =head1 DESCRIPTION This document describes differences between the 5.24.3 release and the 5.24.4 release. If you are upgrading from an earlier release such as 5.24.2, first read L<perl5243delta>, which describes differences between 5.24.2 and 5.24.3. =head1 Security =head2 [CVE-2018-6797] heap-buffer-overflow (WRITE of size 1) in S_regatom (regcomp.c) A crafted regular expression could cause a heap buffer write overflow, with control over the bytes written. L<[perl #132227]|https://rt.perl.org/Public/Bug/Display.html?id=132227> =head2 [CVE-2018-6798] Heap-buffer-overflow in Perl__byte_dump_string (utf8.c) Matching a crafted locale dependent regular expression could cause a heap buffer read overflow and potentially information disclosure. L<[perl #132063]|https://rt.perl.org/Public/Bug/Display.html?id=132063> =head2 [CVE-2018-6913] heap-buffer-overflow in S_pack_rec C<pack()> could cause a heap buffer write overflow with a large item count. L<[perl #131844]|https://rt.perl.org/Public/Bug/Display.html?id=131844> =head2 Assertion failure in Perl__core_swash_init (utf8.c) Control characters in a supposed Unicode property name could cause perl to crash. This has been fixed. L<[perl #132055]|https://rt.perl.org/Public/Bug/Display.html?id=132055> L<[perl #132553]|https://rt.perl.org/Public/Bug/Display.html?id=132553> L<[perl #132658]|https://rt.perl.org/Public/Bug/Display.html?id=132658> =head1 Incompatible Changes There are no changes intentionally incompatible with 5.24.3. If any exist, they are bugs, and we request that you submit a report. See L</Reporting Bugs> below. =head1 Modules and Pragmata =head2 Updated Modules and Pragmata =over 4 =item * L<Module::CoreList> has been upgraded from version 5.20170922_24 to 5.20180414_24. =back =head1 Selected Bug Fixes =over 4 =item * The C<readpipe()> built-in function now checks at compile time that it has only one parameter expression, and puts it in scalar context, thus ensuring that it doesn't corrupt the stack at runtime. L<[perl #4574]|https://rt.perl.org/Public/Bug/Display.html?id=4574> =back =head1 Acknowledgements Perl 5.24.4 represents approximately 7 months of development since Perl 5.24.3 and contains approximately 2,400 lines of changes across 49 files from 12 authors. Excluding auto-generated files, documentation and release tools, there were approximately 1,300 lines of changes to 12 .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.24.4: Abigail, Chris 'BinGOs' Williams, John SJ Anderson, Karen Etheridge, Karl Williamson, Renee Baecker, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook, Yves Orton, Zefram. 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 F<AUTHORS> file in the Perl source distribution. =head1 Reporting Bugs If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at L<https://rt.perl.org/> . There may also be information at L<http://www.perl.org/> , the Perl Home Page. If you believe you have an unreported bug, please run the L<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 C<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 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> for details of how to report the issue. =head1 SEE ALSO The F<Changes> file for an explanation of how to view exhaustive details on what changed. The F<INSTALL> file for how to build Perl. The F<README> file for general stuff. The F<Artistic> and F<Copying> files for copyright information. =cut