perl5263delta(1)

1PERL5263DELTA(1)       Perl Programmers Reference Guide       PERL5263DELTA(1)
2
3
4

NAME

6       perl5263delta - what is new for perl v5.26.3
7

DESCRIPTION

9       This document describes differences between the 5.26.2 release and the
10       5.26.3 release.
11
12       If you are upgrading from an earlier release such as 5.26.1, first read
13       perl5262delta, which describes differences between 5.26.1 and 5.26.2.
14

Security

16   [CVE-2018-12015] Directory traversal in module Archive::Tar
17       By default, Archive::Tar doesn't allow extracting files outside the
18       current working directory.  However, this secure extraction mode could
19       be bypassed by putting a symlink and a regular file with the same name
20       into the tar file.
21
22       [GH #16580] <https://github.com/Perl/perl5/issues/16580> [cpan #125523]
23       <https://rt.cpan.org/Ticket/Display.html?id=125523>
24
25   [CVE-2018-18311] Integer overflow leading to buffer overflow and
26       segmentation fault
27       Integer arithmetic in "Perl_my_setenv()" could wrap when the combined
28       length of the environment variable name and value exceeded around
29       0x7fffffff.  This could lead to writing beyond the end of an allocated
30       buffer with attacker supplied data.
31
32       [GH #16560] <https://github.com/Perl/perl5/issues/16560>
33
34   [CVE-2018-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)
35       A crafted regular expression could cause heap-buffer-overflow write
36       during compilation, potentially allowing arbitrary code execution.
37
38       [GH #16649] <https://github.com/Perl/perl5/issues/16649>
39
40   [CVE-2018-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c)
41       A crafted regular expression could cause heap-buffer-overflow read
42       during compilation, potentially leading to sensitive information being
43       leaked.
44
45       [GH #16554] <https://github.com/Perl/perl5/issues/16554>
46
47   [CVE-2018-18314] Heap-buffer-overflow write in S_regatom (regcomp.c)
48       A crafted regular expression could cause heap-buffer-overflow write
49       during compilation, potentially allowing arbitrary code execution.
50
51       [GH #16041] <https://github.com/Perl/perl5/issues/16041>
52

Incompatible Changes

54       There are no changes intentionally incompatible with 5.26.2.  If any
55       exist, they are bugs, and we request that you submit a report.  See
56       "Reporting Bugs" below.
57

Modules and Pragmata

59   Updated Modules and Pragmata
60       •   Archive::Tar has been upgraded from version 2.24 to 2.24_01.
61
62       •   Module::CoreList has been upgraded from version 5.20180414_26 to
63           5.20181129_26.
64

Diagnostics

66       The following additions or changes have been made to diagnostic output,
67       including warnings and fatal error messages.  For the complete list of
68       diagnostic messages, see perldiag.
69
70   New Diagnostics
71       New Errors
72
73       •   Unexpected ']' with no following ')' in (?[... in regex; marked by
74           <-- HERE in m/%s/
75
76           (F) While parsing an extended character class a ']' character was
77           encountered at a point in the definition where the only legal use
78           of ']' is to close the character class definition as part of a
79           '])', you may have forgotten the close paren, or otherwise confused
80           the parser.
81
82       •   Expecting close paren for nested extended charclass in regex;
83           marked by <-- HERE in m/%s/
84
85           (F) While parsing a nested extended character class like:
86
87               (?[ ... (?flags:(?[ ... ])) ... ])
88                                        ^
89
90           we expected to see a close paren ')' (marked by ^) but did not.
91
92       •   Expecting close paren for wrapper for nested extended charclass in
93           regex; marked by <-- HERE in m/%s/
94
95           (F) While parsing a nested extended character class like:
96
97               (?[ ... (?flags:(?[ ... ])) ... ])
98                                         ^
99
100           we expected to see a close paren ')' (marked by ^) but did not.
101
102   Changes to Existing Diagnostics
103       •   Syntax error in (?[...]) in regex; marked by <-- HERE in m/%s/
104
105           This fatal error message has been slightly expanded (from "Syntax
106           error in (?[...]) in regex m/%s/") for greater clarity.
107

Acknowledgements

109       Perl 5.26.3 represents approximately 8 months of development since Perl
110       5.26.2 and contains approximately 4,500 lines of changes across 51
111       files from 15 authors.
112
113       Excluding auto-generated files, documentation and release tools, there
114       were approximately 770 lines of changes to 10 .pm, .t, .c and .h files.
115
116       Perl continues to flourish into its third decade thanks to a vibrant
117       community of users and developers.  The following people are known to
118       have contributed the improvements that became Perl 5.26.3:
119
120       Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari
121       Mannsaaker, David Mitchell, H.Merijn Brand, James E Keenan, John SJ
122       Anderson, Karen Etheridge, Karl Williamson, Sawyer X, Steve Hay, Todd
123       Rinaldo, Tony Cook, Yves Orton.
124
125       The list above is almost certainly incomplete as it is automatically
126       generated from version control history.  In particular, it does not
127       include the names of the (very much appreciated) contributors who
128       reported issues to the Perl bug tracker.
129
130       Many of the changes included in this version originated in the CPAN
131       modules included in Perl's core.  We're grateful to the entire CPAN
132       community for helping Perl to flourish.
133
134       For a more complete list of all of Perl's historical contributors,
135       please see the AUTHORS file in the Perl source distribution.
136

Reporting Bugs

138       If you find what you think is a bug, you might check the perl bug
139       database at <https://rt.perl.org/> .  There may also be information at
140       <http://www.perl.org/> , the Perl Home Page.
141
142       If you believe you have an unreported bug, please run the perlbug
143       program included with your release.  Be sure to trim your bug down to a
144       tiny but sufficient test case.  Your bug report, along with the output
145       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
146       the Perl porting team.
147
148       If the bug you are reporting has security implications which make it
149       inappropriate to send to a publicly archived mailing list, then see
150       "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of
151       how to report the issue.
152

Give Thanks

154       If you wish to thank the Perl 5 Porters for the work we had done in
155       Perl 5, you can do so by running the "perlthanks" program:
156
157           perlthanks
158
159       This will send an email to the Perl 5 Porters list with your show of
160       thanks.
161