perl5144delta (1) - Linux Man Pages
perl5144delta: what is new for perl v5.14.4
perl5144delta - what is new for perl v5.14.4
DESCRIPTIONThis document describes differences between the 5.14.3 release and the 5.14.4 release.
Core EnhancementsNo changes since 5.14.0.
SecurityThis release contains one major, and medium, and a number of minor security fixes. The latter are included mainly to allow the test suite to pass cleanly with the clang compiler's address sanitizer facility.
CVE-2013-1667: memory exhaustion with arbitrary hash keysWith a carefully crafted set of hash keys (for example arguments on a URL), it is possible to cause a hash to consume a large amount of memory and CPU, and thus possibly to achieve a Denial-of-Service.
memory leak in EncodeThe UTF-8 encoding implementation in Encode.xs had a memory leak which has been fixed.
[perl #111594] Socket::unpack_sockaddr_un heap-buffer-overflowA read buffer overflow could occur when copying "sockaddr" buffers. Fairly harmless.
[perl #111586] SDBM_File: fix off-by-one access to global .dirAn extra byte was being copied for some string literals. Fairly harmless.
off-by-two error in List::UtilA string literal was being used that included two bytes beyond the end of the string. Fairly harmless.
[perl #115994] fix segv in regcomp.c:S_join_exact()Under debugging builds, while marking optimised-out regex nodes as type "OPTIMIZED", it could treat blocks of exact text as if they were nodes, and thus SEGV. Fairly harmless.
[perl #115992] PL_eval_start use-after-freeThe statement "local $[;", when preceded by an "eval", and when not part of an assignment, could crash. Fairly harmless.
wrap-around with IO on long stringsReading or writing strings greater than 2**31 bytes in size could segfault due to integer wraparound.
Incompatible ChangesThere are no changes intentionally incompatible with 5.14.0. If any exist, they are bugs and reports are welcome.
DeprecationsThere have been no deprecations since 5.14.0.
Modules and Pragmata
New Modules and PragmataNone
Updated Modules and PragmataThe following modules have just the minor code fixes as listed above in ``Security'' (version numbers have not changed):
Encode has been upgraded from version 2.42_01 to version 2.42_02.
Removed Modules and PragmataNone.
Changes to Existing DocumentationNone.
DiagnosticsNo new or changed diagnostics.
Configuration and CompilationNo changes.
- 5.14.3 failed to compile on VMS due to incomplete application of a patch series that allowed "userelocatableinc" and "usesitecustomize" to be used simultaneously. Other platforms were not affected and the problem has now been corrected.
Selected Bug Fixes
- In Perl 5.14.0, "$tainted ~~ @array" stopped working properly. Sometimes it would erroneously fail (when $tainted contained a string that occurs in the array after the first element) or erroneously succeed (when "undef" occurred after the first element) [perl #93590].
AcknowledgementsPerl 5.14.4 represents approximately 5 months of development since Perl 5.14.3 and contains approximately 1,700 lines of changes across 49 files from 12 authors.
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.14.4:
Andy Dougherty, Chris 'BinGOs' Williams, Christian Hansen, Craig A. Berry, Dave Rolsky, David Mitchell, Dominic Hargreaves, Father Chrysostomos, Florian Ragwitz, Reini Urban, Ricardo Signes, 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.
Reporting BugsIf 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 http://rt.perl.org/perlbug/ . 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 [at] 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 please send it to perl5-security-report [at] perl.org. This points to a closed subscription unarchived mailing list, which includes all the core committers, who be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN.
SEE ALSOThe Changes file for an explanation of how to view exhaustive details on what changed.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.