Debian Codegraph @

upstream/debian-unstable/man1/perl5263delta.1

raw
1 .\" -*- mode: troff; coding: utf-8 -*-
2 .\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
3 .\"
4 .\" Standard preamble:
5 .\" ========================================================================
6 .de Sp \" Vertical space (when we can't use .PP)
7 .if t .sp .5v
8 .if n .sp
9 ..
10 .de Vb \" Begin verbatim text
11 .ft CW
12 .nf
13 .ne \\$1
14 ..
15 .de Ve \" End verbatim text
16 .ft R
17 .fi
18 ..
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
20 .ie n \{\
21 . ds C` ""
22 . ds C' ""
23 'br\}
24 .el\{\
25 . ds C`
26 . ds C'
27 'br\}
28 .\"
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
30 .ie \n(.g .ds Aq \(aq
31 .el .ds Aq '
32 .\"
33 .\" If the F register is >0, we'll generate index entries on stderr for
34 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
37 .\"
38 .\" Avoid warning from groff about undefined register 'F'.
39 .de IX
40 ..
41 .nr rF 0
42 .if \n(.g .if rF .nr rF 1
43 .if (\n(rF:(\n(.g==0)) \{\
44 . if \nF \{\
45 . de IX
46 . tm Index:\\$1\t\\n%\t"\\$2"
47 ..
48 . if !\nF==2 \{\
49 . nr % 0
50 . nr F 2
51 . \}
52 . \}
53 .\}
54 .rr rF
55 .\" ========================================================================
56 .\"
57 .IX Title "PERL5263DELTA 1"
58 .TH PERL5263DELTA 1 2025-11-16 "perl v5.40.1" "Perl Programmers Reference Guide"
59 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
60 .\" way too many mistakes in technical documents.
61 .if n .ad l
62 .nh
63 .SH NAME
64 perl5263delta \- what is new for perl v5.26.3
65 .SH DESCRIPTION
66 .IX Header "DESCRIPTION"
67 This document describes differences between the 5.26.2 release and the 5.26.3
68 release.
69 .PP
70 If you are upgrading from an earlier release such as 5.26.1, first read
71 perl5262delta, which describes differences between 5.26.1 and 5.26.2.
72 .SH Security
73 .IX Header "Security"
74 .SS "[CVE\-2018\-12015] Directory traversal in module Archive::Tar"
75 .IX Subsection "[CVE-2018-12015] Directory traversal in module Archive::Tar"
76 By default, Archive::Tar doesn't allow extracting files outside the current
77 working directory. However, this secure extraction mode could be bypassed by
78 putting a symlink and a regular file with the same name into the tar file.
79 .PP
80 [GH #16580] <https://github.com/Perl/perl5/issues/16580>
81 [cpan #125523] <https://rt.cpan.org/Ticket/Display.html?id=125523>
82 .SS "[CVE\-2018\-18311] Integer overflow leading to buffer overflow and segmentation fault"
83 .IX Subsection "[CVE-2018-18311] Integer overflow leading to buffer overflow and segmentation fault"
84 Integer arithmetic in \f(CWPerl_my_setenv()\fR could wrap when the combined length
85 of the environment variable name and value exceeded around 0x7fffffff. This
86 could lead to writing beyond the end of an allocated buffer with attacker
87 supplied data.
88 .PP
89 [GH #16560] <https://github.com/Perl/perl5/issues/16560>
90 .SS "[CVE\-2018\-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)"
91 .IX Subsection "[CVE-2018-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)"
92 A crafted regular expression could cause heap-buffer-overflow write during
93 compilation, potentially allowing arbitrary code execution.
94 .PP
95 [GH #16649] <https://github.com/Perl/perl5/issues/16649>
96 .SS "[CVE\-2018\-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c)"
97 .IX Subsection "[CVE-2018-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c)"
98 A crafted regular expression could cause heap-buffer-overflow read during
99 compilation, potentially leading to sensitive information being leaked.
100 .PP
101 [GH #16554] <https://github.com/Perl/perl5/issues/16554>
102 .SS "[CVE\-2018\-18314] Heap-buffer-overflow write in S_regatom (regcomp.c)"
103 .IX Subsection "[CVE-2018-18314] Heap-buffer-overflow write in S_regatom (regcomp.c)"
104 A crafted regular expression could cause heap-buffer-overflow write during
105 compilation, potentially allowing arbitrary code execution.
106 .PP
107 [GH #16041] <https://github.com/Perl/perl5/issues/16041>
108 .SH "Incompatible Changes"
109 .IX Header "Incompatible Changes"
110 There are no changes intentionally incompatible with 5.26.2. If any exist,
111 they are bugs, and we request that you submit a report. See
112 "Reporting Bugs" below.
113 .SH "Modules and Pragmata"
114 .IX Header "Modules and Pragmata"
115 .SS "Updated Modules and Pragmata"
116 .IX Subsection "Updated Modules and Pragmata"
117 .IP \(bu 4
118 Archive::Tar has been upgraded from version 2.24 to 2.24_01.
119 .IP \(bu 4
120 Module::CoreList has been upgraded from version 5.20180414_26 to 5.20181129_26.
121 .SH Diagnostics
122 .IX Header "Diagnostics"
123 The following additions or changes have been made to diagnostic output,
124 including warnings and fatal error messages. For the complete list of
125 diagnostic messages, see perldiag.
126 .SS "New Diagnostics"
127 .IX Subsection "New Diagnostics"
128 \fINew Errors\fR
129 .IX Subsection "New Errors"
130 .IP \(bu 4
131 Unexpected ']' with no following ')' in (?[... in regex; marked by <\-\- HERE in m/%s/
132 .Sp
133 (F) While parsing an extended character class a ']' character was encountered
134 at a point in the definition where the only legal use of ']' is to close the
135 character class definition as part of a '])', you may have forgotten the close
136 paren, or otherwise confused the parser.
137 .IP \(bu 4
138 Expecting close paren for nested extended charclass in regex; marked by <\-\- HERE in m/%s/
139 .Sp
140 (F) While parsing a nested extended character class like:
141 .Sp
142 .Vb 2
143 \& (?[ ... (?flags:(?[ ... ])) ... ])
144 \& ^
145 .Ve
146 .Sp
147 we expected to see a close paren ')' (marked by ^) but did not.
148 .IP \(bu 4
149 Expecting close paren for wrapper for nested extended charclass in regex; marked by <\-\- HERE in m/%s/
150 .Sp
151 (F) While parsing a nested extended character class like:
152 .Sp
153 .Vb 2
154 \& (?[ ... (?flags:(?[ ... ])) ... ])
155 \& ^
156 .Ve
157 .Sp
158 we expected to see a close paren ')' (marked by ^) but did not.
159 .SS "Changes to Existing Diagnostics"
160 .IX Subsection "Changes to Existing Diagnostics"
161 .IP \(bu 4
162 Syntax error in (?[...]) in regex; marked by <\-\- HERE in m/%s/
163 .Sp
164 This fatal error message has been slightly expanded (from "Syntax error in
165 (?[...]) in regex m/%s/") for greater clarity.
166 .SH Acknowledgements
167 .IX Header "Acknowledgements"
168 Perl 5.26.3 represents approximately 8 months of development since Perl 5.26.2
169 and contains approximately 4,500 lines of changes across 51 files from 15
170 authors.
171 .PP
172 Excluding auto-generated files, documentation and release tools, there were
173 approximately 770 lines of changes to 10 .pm, .t, .c and .h files.
174 .PP
175 Perl continues to flourish into its third decade thanks to a vibrant community
176 of users and developers. The following people are known to have contributed
177 the improvements that became Perl 5.26.3:
178 .PP
179 Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari Mannsåker, David
180 Mitchell, H.Merijn Brand, James E Keenan, John SJ Anderson, Karen Etheridge,
181 Karl Williamson, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook, Yves Orton.
182 .PP
183 The list above is almost certainly incomplete as it is automatically generated
184 from version control history. In particular, it does not include the names of
185 the (very much appreciated) contributors who reported issues to the Perl bug
186 tracker.
187 .PP
188 Many of the changes included in this version originated in the CPAN modules
189 included in Perl's core. We're grateful to the entire CPAN community for
190 helping Perl to flourish.
191 .PP
192 For a more complete list of all of Perl's historical contributors, please see
193 the \fIAUTHORS\fR file in the Perl source distribution.
194 .SH "Reporting Bugs"
195 .IX Header "Reporting Bugs"
196 If you find what you think is a bug, you might check the perl bug database
197 at <https://rt.perl.org/> . There may also be information at
198 <http://www.perl.org/> , the Perl Home Page.
199 .PP
200 If you believe you have an unreported bug, please run the perlbug program
201 included with your release. Be sure to trim your bug down to a tiny but
202 sufficient test case. Your bug report, along with the output of \f(CW\*(C`perl \-V\*(C'\fR,
203 will be sent off to [email protected] to be analysed by the Perl porting team.
204 .PP
205 If the bug you are reporting has security implications which make it
206 inappropriate to send to a publicly archived mailing list, then see
207 "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec
208 for details of how to report the issue.
209 .SH "Give Thanks"
210 .IX Header "Give Thanks"
211 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
212 you can do so by running the \f(CW\*(C`perlthanks\*(C'\fR program:
213 .PP
214 .Vb 1
215 \& perlthanks
216 .Ve
217 .PP
218 This will send an email to the Perl 5 Porters list with your show of thanks.
219 .SH "SEE ALSO"
220 .IX Header "SEE ALSO"
221 The \fIChanges\fR file for an explanation of how to view exhaustive details on
222 what changed.
223 .PP
224 The \fIINSTALL\fR file for how to build Perl.
225 .PP
226 The \fIREADME\fR file for general stuff.
227 .PP
228 The \fIArtistic\fR and \fICopying\fR files for copyright information.