| 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 "PERL5283DELTA 1" |
| 58 |
.TH PERL5283DELTA 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 |
perl5283delta \- what is new for perl v5.28.3 |
| 65 |
.SH DESCRIPTION |
| 66 |
.IX Header "DESCRIPTION" |
| 67 |
This document describes differences between the 5.28.2 release and the 5.28.3 |
| 68 |
release. |
| 69 |
.PP |
| 70 |
If you are upgrading from an earlier release such as 5.28.1, first read |
| 71 |
perl5282delta, which describes differences between 5.28.1 and 5.28.2. |
| 72 |
.SH Security |
| 73 |
.IX Header "Security" |
| 74 |
.SS "[CVE\-2020\-10543] Buffer overflow caused by a crafted regular expression" |
| 75 |
.IX Subsection "[CVE-2020-10543] Buffer overflow caused by a crafted regular expression" |
| 76 |
A signed \f(CW\*(C`size_t\*(C'\fR integer overflow in the storage space calculations for |
| 77 |
nested regular expression quantifiers could cause a heap buffer overflow in |
| 78 |
Perl's regular expression compiler that overwrites memory allocated after the |
| 79 |
regular expression storage space with attacker supplied data. |
| 80 |
.PP |
| 81 |
The target system needs a sufficient amount of memory to allocate partial |
| 82 |
expansions of the nested quantifiers prior to the overflow occurring. This |
| 83 |
requirement is unlikely to be met on 64\-bit systems. |
| 84 |
.PP |
| 85 |
Discovered by: ManhND of The Tarantula Team, VinCSS (a member of Vingroup). |
| 86 |
.SS "[CVE\-2020\-10878] Integer overflow via malformed bytecode produced by a crafted regular expression" |
| 87 |
.IX Subsection "[CVE-2020-10878] Integer overflow via malformed bytecode produced by a crafted regular expression" |
| 88 |
Integer overflows in the calculation of offsets between instructions for the |
| 89 |
regular expression engine could cause corruption of the intermediate language |
| 90 |
state of a compiled regular expression. An attacker could abuse this behaviour |
| 91 |
to insert instructions into the compiled form of a Perl regular expression. |
| 92 |
.PP |
| 93 |
Discovered by: Hugo van der Sanden and Slaven Rezic. |
| 94 |
.SS "[CVE\-2020\-12723] Buffer overflow caused by a crafted regular expression" |
| 95 |
.IX Subsection "[CVE-2020-12723] Buffer overflow caused by a crafted regular expression" |
| 96 |
Recursive calls to \f(CWS_study_chunk()\fR by Perl's regular expression compiler to |
| 97 |
optimize the intermediate language representation of a regular expression could |
| 98 |
cause corruption of the intermediate language state of a compiled regular |
| 99 |
expression. |
| 100 |
.PP |
| 101 |
Discovered by: Sergey Aleynikov. |
| 102 |
.SS "Additional Note" |
| 103 |
.IX Subsection "Additional Note" |
| 104 |
An application written in Perl would only be vulnerable to any of the above |
| 105 |
flaws if it evaluates regular expressions supplied by the attacker. Evaluating |
| 106 |
regular expressions in this fashion is known to be dangerous since the regular |
| 107 |
expression engine does not protect against denial of service attacks in this |
| 108 |
usage scenario. |
| 109 |
.SH "Incompatible Changes" |
| 110 |
.IX Header "Incompatible Changes" |
| 111 |
There are no changes intentionally incompatible with Perl 5.28.2. If any |
| 112 |
exist, they are bugs, and we request that you submit a report. See |
| 113 |
"Reporting Bugs" below. |
| 114 |
.SH "Modules and Pragmata" |
| 115 |
.IX Header "Modules and Pragmata" |
| 116 |
.SS "Updated Modules and Pragmata" |
| 117 |
.IX Subsection "Updated Modules and Pragmata" |
| 118 |
.IP \(bu 4 |
| 119 |
Module::CoreList has been upgraded from version 5.20190419 to 5.20200601_28. |
| 120 |
.SH Testing |
| 121 |
.IX Header "Testing" |
| 122 |
Tests were added and changed to reflect the other additions and changes in this |
| 123 |
release. |
| 124 |
.SH Acknowledgements |
| 125 |
.IX Header "Acknowledgements" |
| 126 |
Perl 5.28.3 represents approximately 13 months of development since Perl 5.28.2 |
| 127 |
and contains approximately 3,100 lines of changes across 48 files from 16 |
| 128 |
authors. |
| 129 |
.PP |
| 130 |
Excluding auto-generated files, documentation and release tools, there were |
| 131 |
approximately 1,700 lines of changes to 9 .pm, .t, .c and .h files. |
| 132 |
.PP |
| 133 |
Perl continues to flourish into its fourth decade thanks to a vibrant community |
| 134 |
of users and developers. The following people are known to have contributed |
| 135 |
the improvements that became Perl 5.28.3: |
| 136 |
.PP |
| 137 |
Chris 'BinGOs' Williams, Dan Book, Hugo van der Sanden, James E Keenan, John |
| 138 |
Lightsey, Karen Etheridge, Karl Williamson, Matthew Horsfall, Max Maischein, |
| 139 |
Nicolas R., Renee Baecker, Sawyer X, Steve Hay, Tom Hukins, Tony Cook, Zak B. |
| 140 |
Elep. |
| 141 |
.PP |
| 142 |
The list above is almost certainly incomplete as it is automatically generated |
| 143 |
from version control history. In particular, it does not include the names of |
| 144 |
the (very much appreciated) contributors who reported issues to the Perl bug |
| 145 |
tracker. |
| 146 |
.PP |
| 147 |
Many of the changes included in this version originated in the CPAN modules |
| 148 |
included in Perl's core. We're grateful to the entire CPAN community for |
| 149 |
helping Perl to flourish. |
| 150 |
.PP |
| 151 |
For a more complete list of all of Perl's historical contributors, please see |
| 152 |
the \fIAUTHORS\fR file in the Perl source distribution. |
| 153 |
.SH "Reporting Bugs" |
| 154 |
.IX Header "Reporting Bugs" |
| 155 |
If you find what you think is a bug, you might check the perl bug database at |
| 156 |
<https://github.com/Perl/perl5/issues>. There may also be information at |
| 157 |
<https://www.perl.org/>, the Perl Home Page. |
| 158 |
.PP |
| 159 |
If you believe you have an unreported bug, please open an issue at |
| 160 |
<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a |
| 161 |
tiny but sufficient test case. |
| 162 |
.PP |
| 163 |
If the bug you are reporting has security implications which make it |
| 164 |
inappropriate to send to a public issue tracker, then see |
| 165 |
"SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to |
| 166 |
report the issue. |
| 167 |
.SH "Give Thanks" |
| 168 |
.IX Header "Give Thanks" |
| 169 |
If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you |
| 170 |
can do so by running the \f(CW\*(C`perlthanks\*(C'\fR program: |
| 171 |
.PP |
| 172 |
.Vb 1 |
| 173 |
\& perlthanks |
| 174 |
.Ve |
| 175 |
.PP |
| 176 |
This will send an email to the Perl 5 Porters list with your show of thanks. |
| 177 |
.SH "SEE ALSO" |
| 178 |
.IX Header "SEE ALSO" |
| 179 |
The \fIChanges\fR file for an explanation of how to view exhaustive details on |
| 180 |
what changed. |
| 181 |
.PP |
| 182 |
The \fIINSTALL\fR file for how to build Perl. |
| 183 |
.PP |
| 184 |
The \fIREADME\fR file for general stuff. |
| 185 |
.PP |
| 186 |
The \fIArtistic\fR and \fICopying\fR files for copyright information. |