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.
Published: 2017-05-17
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

Tracking

Sign in to view the affected projects.

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

No history.

Subscriptions

Perltidy Project Perltidy
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

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

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

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