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
|
# Security Policy for the Text::CSV_XS distribution.
Report issues via email at: H.Merijn Brand <hmbrand@cpan.org>.
This is the Security Policy for the Perl Text::CSV_XS distribution.
The latest version of the Security Policy can be found in the
[git repository for Text::CSV_XS](https://github.com/Tux/Text-CSV_XS).
This text is based on the CPAN Security Group's Guidelines for Adding
a Security Policy to Perl Distributions (version 1.0.0)
https://security.metacpan.org/docs/guides/security-policy-for-authors.html
# How to Report a Security Vulnerability
Security vulnerabilities can be reported by e-mail to the current
project maintainers at H.Merijn Brand <hmbrand@cpan.org>.
Please include as many details as possible, including code samples
or test cases, so that we can reproduce the issue. Check that your
report does not expose any sensitive data, such as passwords,
tokens, or personal information.
If you would like any help with triaging the issue, or if the issue
is being actively exploited, please copy the report to the CPAN
Security Group (CPANSec) at <cpan-security@security.metacpan.org>.
Please *do not* use the public issue reporting system on RT or
GitHub issues for reporting security vulnerabilities.
Please do not disclose the security vulnerability in public forums
until past any proposed date for public disclosure, or it has been
made public by the maintainers or CPANSec. That includes patches or
pull requests.
For more information, see
[Report a Security Issue](https://security.metacpan.org/docs/report.html)
on the CPANSec website.
## Response to Reports
The maintainer(s) aim to acknowledge your security report as soon as
possible. However, this project is maintained by a single person in
their spare time, and they cannot guarantee a rapid response. If you
have not received a response from them within 10 days, then
please send a reminder to them and copy the report to CPANSec at
<cpan-security@security.metacpan.org>.
Please note that the initial response to your report will be an
acknowledgement, with a possible query for more information. It
will not necessarily include any fixes for the issue.
The project maintainer(s) may forward this issue to the security
contacts for other projects where we believe it is relevant. This
may include embedded libraries, system libraries, prerequisite
modules or downstream software that uses this software.
They may also forward this issue to CPANSec.
# Which Software This Policy Applies To
Any security vulnerabilities in Text::CSV_XS are covered by this policy.
Security vulnerabilities are considered anything that allows users
to execute unauthorised code, access unauthorised resources, or to
have an adverse impact on accessibility or performance of a system.
Security vulnerabilities in upstream software (embedded libraries,
prerequisite modules or system libraries, or in Perl), are not
covered by this policy unless they affect Text::CSV_XS, or Text::CSV_XS can
be used to exploit vulnerabilities in them.
Security vulnerabilities in downstream software (any software that
uses Text::CSV_XS, or plugins to it that are not included with the
Text::CSV_XS distribution) are not covered by this policy.
## Supported Versions of Text::CSV_XS
The maintainer(s) will only commit to releasing security fixes for
the latest version of Text::CSV_XS.
Note that the Text::CSV_XS project only supports major versions of Perl
released in the past 5 years, even though Text::CSV_XS will run on
older versions of Perl. If a security fix requires us to increase
the minimum version of Perl that is supported, then we may do so.
# Installation and Usage Issues
The distribution metadata specifies minimum versions of
prerequisites that are required for Text::CSV_XS to work. However, some
of these prerequisites may have security vulnerabilities, and you
should ensure that you are using up-to-date versions of these
prerequisites.
Where security vulnerabilities are known, the metadata may indicate
newer versions as recommended.
## Usage
Please see the software documentation for further information.
|
