Debian Codegraph @

upstream/mageia-cauldron/man1/perlsecpolicy.1

raw
1 .\" -*- mode: troff; coding: utf-8 -*-
2 .\" Automatically generated by Pod::Man v6.0.2 (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 .\" Required to disable full justification in groff 1.23.0.
57 .if n .ds AD l
58 .\" ========================================================================
59 .\"
60 .IX Title "PERLSECPOLICY 1"
61 .TH PERLSECPOLICY 1 2025-06-24 "perl v5.42.0" "Perl Programmers Reference Guide"
62 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
63 .\" way too many mistakes in technical documents.
64 .if n .ad l
65 .nh
66 .SH NAME
67 perlsecpolicy \- Perl security report handling policy
68 .SH DESCRIPTION
69 .IX Header "DESCRIPTION"
70 The Perl project takes security issues seriously.
71 .PP
72 The responsibility for handling security reports in a timely and
73 effective manner has been delegated to a security team composed
74 of a subset of the Perl core developers.
75 .PP
76 This document describes how the Perl security team operates and
77 how the team evaluates new security reports.
78 .SH "REPORTING SECURITY ISSUES IN PERL"
79 .IX Header "REPORTING SECURITY ISSUES IN PERL"
80 If you believe you have found a security vulnerability in the Perl
81 interpreter or modules maintained in the core Perl codebase,
82 email the details to
83 perl\[email protected] <mailto:[email protected]>.
84 This address is a closed membership mailing list monitored by the Perl
85 security team.
86 .PP
87 You should receive an initial response to your report within 72 hours.
88 If you do not receive a response in that time, please contact
89 the Perl Steering Council <mailto:[email protected]>.
90 .PP
91 When members of the security team reply to your messages, they will
92 generally include the perl\[email protected] address in the "To" or "CC"
93 fields of the response. This allows all of the security team to follow
94 the discussion and chime in as needed. Use the "Reply\-all" functionality
95 of your email client when you send subsequent responses so that the
96 entire security team receives the message.
97 .PP
98 The security team will evaluate your report and make an initial
99 determination of whether it is likely to fit the scope of issues the
100 team handles. General guidelines about how this is determined are
101 detailed in the "WHAT ARE SECURITY ISSUES" section.
102 .PP
103 If your report meets the team\*(Aqs criteria, you will be provided the issue\*(Aqs
104 CVE ID(s). Issue identifiers have the form CVE\-YYYY\-NNNNN, where YYYY is the
105 year the CVE was reported, and NNNNN is a unique number. Include this identifier
106 with any subsequent messages you send.
107 .PP
108 The security team will send periodic updates about the status of your
109 issue and guide you through any further action that is required to complete
110 the vulnerability remediation process. The stages vulnerabilities typically
111 go through are explained in the "HOW WE DEAL WITH SECURITY ISSUES"
112 section.
113 .SH "WHAT ARE SECURITY ISSUES"
114 .IX Header "WHAT ARE SECURITY ISSUES"
115 A vulnerability is a behavior of a software system that compromises the
116 system\*(Aqs expected confidentiality, integrity or availability protections.
117 .PP
118 A security issue is a bug in one or more specific components of a software
119 system that creates a vulnerability.
120 .PP
121 Software written in the Perl programming language is typically composed
122 of many layers of software written by many different groups. It can be
123 very complicated to determine which specific layer of a complex real\-world
124 application was responsible for preventing a vulnerable behavior, but this
125 is an essential part of fixing the vulnerability.
126 .SS "Software covered by the Perl security team"
127 .IX Subsection "Software covered by the Perl security team"
128 The Perl security team handles security issues in:
129 .IP \(bu 4
130 The Perl interpreter
131 .IP \(bu 4
132 The Perl modules shipped with the interpreter that are developed in the core
133 Perl repository
134 .IP \(bu 4
135 The command line tools shipped with the interpreter that are developed in the
136 core Perl repository
137 .PP
138 Files under the \fIcpan/\fR directory in Perl\*(Aqs repository and release tarballs are
139 developed and maintained independently. The Perl security team does not
140 directly handle security issues for these modules, but since this code is
141 bundled with Perl, we will assist in forwarding the issue to the relevant
142 maintainer(s) and you can still report these issues to us in secrecy.
143 .SS "Bugs that may qualify as security issues in Perl"
144 .IX Subsection "Bugs that may qualify as security issues in Perl"
145 Perl is designed to be a fast and flexible general purpose programming
146 language. The Perl interpreter and Perl modules make writing safe and
147 secure applications easy, but they do have limitations.
148 .PP
149 As a general rule, a bug in Perl needs to meet all of the following
150 criteria to be considered a security issue:
151 .IP \(bu 4
152 The vulnerable behavior is not mentioned in Perl\*(Aqs documentation
153 or public issue tracker.
154 .IP \(bu 4
155 The vulnerable behavior is not implied by an expected behavior.
156 .IP \(bu 4
157 The vulnerable behavior is not a generally accepted limitation of
158 the implementation.
159 .IP \(bu 4
160 The vulnerable behavior is likely to be exposed to attack in
161 otherwise secure applications written in Perl.
162 .IP \(bu 4
163 The vulnerable behavior provides a specific tangible benefit
164 to an attacker that triggers the behavior.
165 .SS "Bugs that do not qualify as security issues in Perl"
166 .IX Subsection "Bugs that do not qualify as security issues in Perl"
167 There are certain categories of bugs that are frequently reported to
168 the security team that do not meet the criteria listed above.
169 .PP
170 The following is a list of commonly reported bugs that are not
171 handled as security issues.
172 .PP
173 \fIFeeding untrusted code to the interpreter\fR
174 .IX Subsection "Feeding untrusted code to the interpreter"
175 .PP
176 The Perl parser is not designed to evaluate untrusted code.
177 If your application requires the evaluation of untrusted code, it
178 should rely on an operating system level sandbox for its security.
179 .PP
180 \fIStack overflows due to excessive recursion\fR
181 .IX Subsection "Stack overflows due to excessive recursion"
182 .PP
183 Excessive recursion is often caused by code that does
184 not enforce limits on inputs. The Perl interpreter assumes limits
185 on recursion will be enforced by the application.
186 .PP
187 \fIOut of memory errors\fR
188 .IX Subsection "Out of memory errors"
189 .PP
190 Common Perl constructs such as \f(CW\*(C`pack\*(C'\fR, the \f(CW\*(C`x\*(C'\fR operator,
191 and regular expressions accept numeric quantifiers that control how
192 much memory will be allocated to store intermediate values or results.
193 If you allow an attacker to supply these quantifiers and consume all
194 available memory, the Perl interpreter will not prevent it.
195 .PP
196 \fIEscape from a Safe compartment\fR
197 .IX Subsection "Escape from a Safe compartment"
198 .PP
199 Opcode restrictions and Safe compartments are not supported as
200 security mechanisms. The Perl parser is not designed to evaluate
201 untrusted code.
202 .PP
203 \fIUse of the \fR\f(CI\*(C`p\*(C'\fR\fI and \fR\f(CI\*(C`P\*(C'\fR\fI pack templates\fR
204 .IX Subsection "Use of the p and P pack templates"
205 .PP
206 These templates are unsafe by design.
207 .PP
208 \fIStack not reference\-counted issues\fR
209 .IX Subsection "Stack not reference-counted issues"
210 .PP
211 These bugs typically present as use\-after\-free errors or as assertion
212 failures on the type of a \f(CW\*(C`SV\*(C'\fR. Stack not reference\-counted
213 crashes usually occur because code is both modifying a reference or
214 glob and using the values referenced by that glob or reference.
215 .PP
216 This type of bug is a long standing issue with the Perl interpreter
217 that seldom occurs in normal code. Examples of this type of bug
218 generally assume that attacker\-supplied code will be evaluated by
219 the Perl interpreter.
220 .PP
221 \fIThawing attacker\-supplied data with Storable\fR
222 .IX Subsection "Thawing attacker-supplied data with Storable"
223 .PP
224 Storable is designed to be a very fast serialization format.
225 It is not designed to be safe for deserializing untrusted inputs.
226 .PP
227 \fIUsing attacker supplied SDBM_File databases\fR
228 .IX Subsection "Using attacker supplied SDBM_File databases"
229 .PP
230 The SDBM_File module is not intended for use with untrusted SDBM
231 databases.
232 .PP
233 \fIBadly encoded UTF\-8 flagged scalars\fR
234 .IX Subsection "Badly encoded UTF-8 flagged scalars"
235 .PP
236 This type of bug occurs when the \f(CW\*(C`:utf8\*(C'\fR PerlIO layer is used to
237 read badly encoded data, or other mechanisms are used to directly
238 manipulate the UTF\-8 flag on an SV.
239 .PP
240 A badly encoded UTF\-8 flagged SV is not a valid SV. Code that
241 creates SV\*(Aqs in this fashion is corrupting Perl\*(Aqs internal state.
242 .PP
243 \fIIssues that exist only in blead, or in a release candidate\fR
244 .IX Subsection "Issues that exist only in blead, or in a release candidate"
245 .PP
246 The blead branch and Perl release candidates do not receive security
247 support. Security defects that are present only in pre\-release
248 versions of Perl are handled through the normal bug reporting and
249 resolution process.
250 .PP
251 \fICPAN modules or other Perl project resources\fR
252 .IX Subsection "CPAN modules or other Perl project resources"
253 .PP
254 The Perl security team is focused on the Perl interpreter and modules
255 maintained in the core Perl codebase. The team has no special access
256 to fix CPAN modules, applications written in Perl, Perl project websites,
257 Perl mailing lists or the Perl IRC servers.
258 .PP
259 \fIEmulated POSIX behaviors on Windows systems\fR
260 .IX Subsection "Emulated POSIX behaviors on Windows systems"
261 .PP
262 The Perl interpreter attempts to emulate \f(CW\*(C`fork\*(C'\fR, \f(CW\*(C`system\*(C'\fR, \f(CW\*(C`exec\*(C'\fR
263 and other POSIX behaviors on Windows systems. This emulation has many
264 quirks that are extensively documented in Perl\*(Aqs public issue tracker.
265 Changing these behaviors would cause significant disruption for existing
266 users on Windows.
267 .SS "Bugs that require special categorization"
268 .IX Subsection "Bugs that require special categorization"
269 Some bugs in the Perl interpreter occur in areas of the codebase that are
270 both security sensitive and prone to failure during normal usage.
271 .PP
272 \fIRegular expressions\fR
273 .IX Subsection "Regular expressions"
274 .PP
275 Untrusted regular expressions are generally safe to compile and match against
276 with several caveats. The following behaviors of Perl\*(Aqs regular expression
277 engine are the developer\*(Aqs responsibility to constrain.
278 .PP
279 The evaluation of untrusted regular expressions while \f(CW\*(C`use re \*(Aqeval\*(Aq;\*(C'\fR is
280 in effect is never safe.
281 .PP
282 Regular expressions are not guaranteed to compile or evaluate in any specific
283 finite time frame.
284 .PP
285 Regular expressions may consume all available system memory when they are
286 compiled or evaluated.
287 .PP
288 Regular expressions may cause excessive recursion that halts the perl
289 interpreter.
290 .PP
291 As a general rule, do not expect Perl\*(Aqs regular expression engine to
292 be resistant to denial of service attacks.
293 .PP
294 \fIDB_File, ODBM_File, or GDBM_File databases\fR
295 .IX Subsection "DB_File, ODBM_File, or GDBM_File databases"
296 .PP
297 These modules rely on external libraries to interact with database files.
298 .PP
299 Bugs caused by reading and writing these file formats are generally caused
300 by the underlying library implementation and are not security issues in
301 Perl.
302 .PP
303 Bugs where Perl mishandles unexpected valid return values from the underlying
304 libraries may qualify as security issues in Perl.
305 .PP
306 \fIAlgorithmic complexity attacks\fR
307 .IX Subsection "Algorithmic complexity attacks"
308 .PP
309 The perl interpreter is reasonably robust to algorithmic complexity
310 attacks. It is not immune to them.
311 .PP
312 Algorithmic complexity bugs that depend on the interpreter processing
313 extremely large amounts of attacker supplied data are not generally handled
314 as security issues.
315 .PP
316 See "Algorithmic Complexity Attacks" in perlsec for additional information.
317 .SH "HOW WE DEAL WITH SECURITY ISSUES"
318 .IX Header "HOW WE DEAL WITH SECURITY ISSUES"
319 The Perl security team follows responsible disclosure practices. Security issues
320 are kept secret until a fix is readily available for most users. This minimizes
321 inherent risks users face from vulnerabilities in Perl.
322 .PP
323 Hiding problems from the users temporarily is a necessary trade\-off to keep
324 them safe. Hiding problems from users permanently is not the goal.
325 .PP
326 When you report a security issue privately to the
327 perl\[email protected] <mailto:[email protected]> contact address, we
328 normally expect you to follow responsible disclosure practices in the handling
329 of the report. If you are unable or unwilling to keep the issue secret until
330 a fix is available to users you should state this clearly in the initial
331 report.
332 .PP
333 The security team\*(Aqs vulnerability remediation workflow is intended to be as
334 open and transparent as possible about the state of your security report.
335 .SS "Perl\*(Aqs vulnerability remediation workflow"
336 .IX Subsection "Perl's vulnerability remediation workflow"
337 \fIInitial contact\fR
338 .IX Subsection "Initial contact"
339 .PP
340 New vulnerability reports will receive an initial reply within 72 hours
341 from the time they arrive at the security team\*(Aqs mailing list. If you do
342 not receive any response in that time, contact the
343 Perl Steering Council <mailto:[email protected]>.
344 .PP
345 The initial response sent by the security team will confirm your message was
346 received and provide an estimated time frame for the security team\*(Aqs
347 triage analysis.
348 .PP
349 \fIInitial triage\fR
350 .IX Subsection "Initial triage"
351 .PP
352 The security team will evaluate the report and determine whether or not
353 it is likely to meet the criteria for handling as a security issue.
354 .PP
355 The security team aims to complete the initial report triage within
356 two weeks\*(Aq time. Complex issues that require significant discussion or
357 research may take longer.
358 .PP
359 If the security report cannot be reproduced or does not meet the team\*(Aqs
360 criteria for handling as a security issue, you will be notified by email
361 and given an opportunity to respond.
362 .PP
363 \fICVE assignment\fR
364 .IX Subsection "CVE assignment"
365 .PP
366 Security reports that pass initial triage analysis are turned into CVEs.
367 When a report progresses to this point, one or more CVEs are reserved by
368 the security team. Issue identifiers have the form CVE\-YYYY\-NNNNN, where
369 YYYY is the year the CVE was reported, and NNNNN is a unique number. The
370 CVE will be used in any subsequent communications about the issue.
371 .PP
372 The assignment of these IDs do not confirm that a security report represents
373 a vulnerability in Perl. Many reports require further analysis to reach that
374 determination. The vulnerability should not be discussed publicly at this stage.
375 .PP
376 An internal ticket will also be opened. These identifiers have the format
377 perl\-security#NNN or Perl/perl\-security#NNN.
378 .PP
379 Issues in the security team\*(Aqs private tracker are used to collect details
380 about the problem and track progress towards a resolution. These notes and
381 other details are not made public when the issue is resolved. Keeping the
382 issue notes private allows the security team to freely discuss attack
383 methods, attack tools, and other related private issues.
384 .PP
385 \fIDevelopment of patches\fR
386 .IX Subsection "Development of patches"
387 .PP
388 Members of the security team will inspect the report and related code in
389 detail to produce fixes for supported versions of Perl.
390 .PP
391 If the team discovers that the reported issue does not meet the team\*(Aqs
392 criteria at this stage, you will be notified by email and given an
393 opportunity to respond before the issue is closed.
394 .PP
395 The team may discuss potential fixes with you or provide you with
396 patches for testing purposes during this time frame.
397 .PP
398 \fIThe CVE is drafted\fR
399 .IX Subsection "The CVE is drafted"
400 .PP
401 Once an issue is fully confirmed and a potential fix has been found,
402 the security team will communicate with the
403 CPAN Security Group CNA <https://security.metacpan.org/>.
404 .PP
405 Details like the range of vulnerable Perl versions and identities
406 of the people that discovered the flaw need to be collected.
407 .PP
408 The security team may ask you to clarify the exact name we should use
409 when crediting discovery of the issue. The
410 "Vulnerability credit and bounties" section of this document
411 explains our preferred format for this credit.
412 .PP
413 \fIPre\-release notifications\fR
414 .IX Subsection "Pre-release notifications"
415 .PP
416 When the security team is satisfied that the fix for a security issue
417 is ready to release publicly, a pre\-release notification announcement
418 is sent to the Openwall Distros List <https://oss-security.openwall.org/wiki/mailing-lists/distros>.
419 Additional other repackagers are notified.
420 .PP
421 NOTE: Any embargoed information sent to the Openwall Distros List
422 expires within 2 weeks of disclosure to that location.
423 .PP
424 This pre\-release announcement includes a list of Perl versions that
425 are affected by the flaw, an analysis of the risks to users, patches
426 the security team has produced, and any information about mitigations
427 or backporting fixes to older versions of Perl that the security team
428 has available.
429 .PP
430 The pre\-release announcement will include a specific target date
431 when the issue will be announced publicly. The time frame between
432 the pre\-release announcement and the release date allows redistributors
433 to prepare and test their own updates and announcements. During this
434 period the vulnerability details and fixes are embargoed (see "Embargo Period" )
435 and should not be shared publicly. This "Embargo Period" may be extended further if
436 problems are discovered during testing.
437 .PP
438 You will be sent the portions of pre\-release announcements that are
439 relevant to the specific issue you reported. This email will include
440 the target release date. Additional updates will be sent if the
441 target release date changes.
442 .PP
443 \fIPre\-release testing\fR
444 .IX Subsection "Pre-release testing"
445 .PP
446 The Perl security team does not directly produce official Perl
447 releases. The team releases security fixes by placing commits
448 in Perl\*(Aqs public git repository and sending announcements.
449 .PP
450 Many users and redistributors prefer using official Perl releases
451 rather than applying patches to an older release. The security
452 team works with Perl\*(Aqs release managers to make this possible.
453 .PP
454 New official releases of Perl are generally produced and tested
455 on private systems during the pre\-release "Embargo Period".
456 .PP
457 \fIRelease of fixes and announcements\fR
458 .IX Subsection "Release of fixes and announcements"
459 .PP
460 The "Embargo Period" ends when the security fixes are committed to Perl\*(Aqs
461 public git repository. Announcements will be sent to the
462 perl5\-porters <https://lists.perl.org/list/perl5-porters.html> and
463 oss\-security <https://oss-security.openwall.org/wiki/mailing-lists/oss-security>
464 mailing lists.
465 .PP
466 If official Perl releases are ready, they will be published at this time
467 and announced on the perl5\-porters <https://lists.perl.org/list/perl5-porters.html>
468 mailing list.
469 .PP
470 The security team will send a follow\-up notification to everyone that
471 participated in the pre\-release "Embargo Period" once the release process is
472 finished. Vulnerability reporters and Perl redistributors should not publish
473 their own announcements or fixes until the Perl security team\*(Aqs release process
474 is complete.
475 .SS "Publicly known and zero\-day security issues"
476 .IX Subsection "Publicly known and zero-day security issues"
477 The security team\*(Aqs vulnerability remediation workflow assumes that issues
478 are reported privately and kept secret until they are resolved. This isn\*(Aqt
479 always the case and information occasionally leaks out before a fix is ready.
480 .PP
481 In these situations the team must decide whether operating in secret increases
482 or decreases the risk to users of Perl. In some cases being open about
483 the risk a security issue creates will allow users to defend against it,
484 in other cases calling attention to an unresolved security issue will
485 make it more likely to be misused.
486 .PP
487 \fIZero\-day security issues\fR
488 .IX Subsection "Zero-day security issues"
489 .PP
490 If an unresolved critical security issue in Perl is being actively abused to
491 attack systems the security team will send out announcements as rapidly as
492 possible with any mitigations the team has available.
493 .PP
494 Perl\*(Aqs public defect tracker will be used to handle the issue so that additional
495 information, fixes, and CVE IDs are visible to affected users as rapidly as
496 possible.
497 .PP
498 \fIOther leaks of security issue information\fR
499 .IX Subsection "Other leaks of security issue information"
500 .PP
501 Depending on the prominence of the information revealed about a security
502 issue and the issue\*(Aqs risk of becoming a zero\-day attack, the security team may
503 skip all or part of its normal remediation workflow.
504 .PP
505 If the security team learns of a significant security issue after it has been
506 identified and resolved in Perl\*(Aqs public issue tracker, the team will
507 request a CVE ID and send an announcement to inform users.
508 .SS "Vulnerability credit and bounties"
509 .IX Subsection "Vulnerability credit and bounties"
510 The Perl project appreciates the effort security researchers invest in making
511 Perl safe and secure.
512 .PP
513 Since much of this work is hidden from the public, crediting researchers
514 publicly is an important part of the vulnerability remediation process.
515 .PP
516 \fICredits in vulnerability announcements\fR
517 .IX Subsection "Credits in vulnerability announcements"
518 .PP
519 When security issues are fixed we will attempt to credit the specific
520 researcher(s) that discovered the flaw in our announcements.
521 .PP
522 Credits are announced using the researcher\*(Aqs preferred full name.
523 .PP
524 If the researcher\*(Aqs contributions were funded by a specific company or
525 part of an organized vulnerability research project, we will include
526 a short name for this group at the researcher\*(Aqs request.
527 .PP
528 Perl\*(Aqs announcements are written in the English language using the 7bit
529 ASCII character set to be reproducible in a variety of formats. We
530 do not include hyperlinks, domain names or marketing material with these
531 acknowledgments.
532 .PP
533 In the event that proper credit for vulnerability discovery cannot be
534 established or there is a disagreement between the Perl security team
535 and the researcher about how the credit should be given, it will be
536 omitted from announcements.
537 .PP
538 \fIBounties for Perl vulnerabilities\fR
539 .IX Subsection "Bounties for Perl vulnerabilities"
540 .PP
541 The Perl project is a non\-profit volunteer effort. We do not provide
542 any monetary rewards for reporting security issues in Perl.
543 .SS "Embargo Period"
544 .IX Subsection "Embargo Period"
545 In the context of Perl\*(Aqs coordinated vulnerability disclosure process, an "embargo"
546 refers to the period of time during which information about a reported vulnerability
547 is kept confidential. This embargo begins when a security issue is reported to the
548 Perl security team and lasts until a fix has been developed and a fix is provided
549 in a public location.
550 .PP
551 The purpose of the embargo is to allow the security team to work on a fix
552 and prepare a coordinated release without the risk of the vulnerability being
553 exploited or disclosed prematurely. This helps ensure that users of Perl
554 and its modules are protected from potential attacks while the security
555 issue is being addressed.
556 .PP
557 Embargo lengths can vary depending on the complexity of the issue and the
558 time required to develop a fix. The security team will communicate
559 the expected duration of the embargo to the reporter and any other
560 parties involved in the process.
561 .PP
562 As a goal, the security team aims to keep the total embargo period to less
563 than 60 days. This may be extended due to the following factors:
564 .IP \(bu 4
565 The complexity of the issue
566 .IP \(bu 4
567 The time required to develop a fix
568 .IP \(bu 4
569 The need for additional testing or validation
570 .IP \(bu 4
571 The availability of resources to address the issue
572 .IP \(bu 4
573 Public holidays which might affect the ability of end users to apply the fix.
574 .PP
575 During this period:
576 .IP \(bu 4
577 Details of the vulnerability are shared only with a restricted group of trusted contributors
578 (such as core maintainers, toolchain maintainers, and packagers), solely for the purpose
579 of preparing and testing a fix.
580 .IP \(bu 4
581 Reporters are asked not to disclose the issue publicly or share details with third parties
582 until the embargo is lifted.
583 .IP \(bu 4
584 The duration of the embargo may vary depending on the severity and complexity of the issue,
585 but typically lasts until the relevant security patch is released and announced.
586 .IP \(bu 4
587 Breaking the embargo — by prematurely disclosing details — undermines the coordinated
588 disclosure process and can hinder the coordinated effort to protect users effectively.
589 .PP
590 The Perl security team strives to resolve vulnerabilities promptly and encourages all parties
591 to respect the embargo period to help protect users and downstream distributions.
592 .SS "Example Release Process"
593 .IX Subsection "Example Release Process"
594 This section provides an example of how a security issue reported by a third
595 party might be handled by the Perl security team, from the initial report to
596 the final release.
597 .PP
598 \fIStep 1: Reporting the Vulnerability\fR
599 .IX Subsection "Step 1: Reporting the Vulnerability"
600 .PP
601 A security researcher discovers a vulnerability in the Perl interpreter that
602 allows an attacker to cause a denial of service under specific conditions. The
603 researcher emails the details of the issue to
604 perl\[email protected] <mailto:[email protected]>, including a
605 proof\-of\-concept script and a description of the impact.
606 .PP
607 \fIStep 2: Initial Response\fR
608 .IX Subsection "Step 2: Initial Response"
609 .PP
610 Within 72 hours, the security team acknowledges receipt of the report and
611 confirms that the issue is under investigation. The researcher is informed of
612 the expected timeline for triage.
613 .PP
614 \fIStep 3: Initial Triage\fR
615 .IX Subsection "Step 3: Initial Triage"
616 .PP
617 The security team reproduces the issue using the provided proof\-of\-concept and
618 determines that it meets the criteria for handling as a security issue. One or
619 more CVEs are reserved in coordination with the
620 CPAN Security Group CNA <https://security.metacpan.org/2025/02/25/cpansec-is-cna-for-perl-and-cpan.html>.
621 The team notifies the researcher referencing the CVE IDs.
622 .PP
623 \fIStep 4: Development of a Fix\fR
624 .IX Subsection "Step 4: Development of a Fix"
625 .PP
626 The security team analyzes the affected code and develops a patch to address
627 the vulnerability. The patch is tested against various scenarios to ensure it
628 resolves the issue without introducing regressions. The researcher is invited
629 to test the patch privately and provide feedback.
630 .PP
631 \fIStep 5: Pre\-Release Notification\fR
632 .IX Subsection "Step 5: Pre-Release Notification"
633 .PP
634 The security team prepares a pre\-release notification, including details of
635 the vulnerability, the affected Perl versions, and the patch. This notification
636 is sent to major redistributors of Perl under embargo, giving them time to
637 prepare their own updates.
638 .PP
639 \fIStep 6: Pre\-Release Testing\fR
640 .IX Subsection "Step 6: Pre-Release Testing"
641 .PP
642 During the remaining embargo period, pre\-notified redistributors prepare packages
643 for release and test the patch to ensure compatibility with their systems.
644 .PP
645 \fIStep 7: Public Release\fR
646 .IX Subsection "Step 7: Public Release"
647 .PP
648 On the scheduled release date, the patch is committed to Perl\*(Aqs public git
649 repository. An official announcement is sent to the
650 perl5\-porters <https://lists.perl.org/list/perl5-porters.html> and
651 oss\-security <https://oss-security.openwall.org/wiki/mailing-lists/oss-security>
652 mailing lists. If applicable, a new Perl release containing the fix is
653 published.
654 .PP
655 The security team will notify CPAN Security Group CNA to publish the CVE.
656 .PP
657 \fIStep 8: Vendor and Third\-Party Updates\fR
658 .IX Subsection "Step 8: Vendor and Third-Party Updates"
659 .PP
660 Vendors and third\-party maintainers incorporate the patch or updated Perl
661 release into their distributions. The security team follows up with all
662 parties involved to ensure the issue is resolved and users are protected.