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.
Advisories
Source ID Title
EUVD EUVD EUVD-2016-1556 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.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-09-17T02:27:13.650Z

Reserved: 2017-05-17T00:00:00Z

Link: CVE-2016-10374

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-05-17T19:29:00.117

Modified: 2025-04-20T01:37:25.860

Link: CVE-2016-10374

cve-icon Redhat

Severity : Low

Publid Date: 2016-08-13T00:00:00Z

Links: CVE-2016-10374 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses