perltidy: Uses current working directory without symlink-attack protection
Published May 17, 2017
5.5
MEDIUMCVSS 3.1
EPSS 0.32%
Description
perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.
Affected products
No data.
- ≤ 2016-03-02
No data.
Red Hat Enterprise Linux 6
perltidy
Will not fix
Red Hat Enterprise Linux 7
perltidy
Will not fix
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | perltidy | Will not fix | n/a |
| Red Hat Enterprise Linux 7 | perltidy | Will not fix | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
AV:L/AC:L/Au:N/C:N/I:P/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (9 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.32% (0.00320) | 22.68th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.32% (0.00320) | 23.54th | v5 (v2026.06.15) |
| Mar 17, 2025 | 0.05% (0.00048) | 12.04th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.04% (0.00042) | 5.07th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.04% (0.00042) | 5.63th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Sep 10, 2022 | 0.89% (0.00885) | 26.24th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.89% (0.00885) | 24.24th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.89% (0.00885) | 10.50th | v2 (v2022.01.01) |
References (5)
- https://access.redhat.com/security/cve/CVE-2016-10374 Vendor Advisory
- https://bugs.debian.org/862667 x_refsource_CONFIRMIssue TrackingThird Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1452050 Issue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2016-10374
- https://www.cve.org/CVERecord?id=CVE-2016-10374
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2016-10374 | Vendor Advisory | |
| https://bugs.debian.org/862667 | x_refsource_CONFIRMIssue TrackingThird Party Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1452050 | Issue Tracking | |
| https://nvd.nist.gov/vuln/detail/CVE-2016-10374 | ||
| https://www.cve.org/CVERecord?id=CVE-2016-10374 |
Change history (0)
No recorded changes yet.