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