CVE-2016-10374 - CVE House
Back to Database
Status published Medium CVE-2016-10374

perltidy through 20160302, as used by perlcritic, check-all-the-things, and other...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2016-10374

Credits & Attribution

No credits recorded in the NVD database.

References

More from perltidy project

View All →
CVE-2014-2277
The make_temporary_filename function in perltidy 20120701-1 and earlier allows local...
High 7.1

Affected Vendor

perltidy project

View all reports →

Affected Software

perltidy
Vulnerable Versions:
0

Timeline

Official Publish: May 17th, 2017
Last Modified: September 17th, 2024
Added to House: July 20th, 2026

CVSS Vectors

V3: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.