CVE-2016-10374

perltidy: Uses current working directory without symlink-attack protection

Published May 17, 2017 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

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.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Sep 17, 2024, 2:27 AM
Reserved
May 17, 2017, 12:00 AM
Status
Modified
Published
May 17, 2017, 7:29 PM
Modified
Jun 17, 2026, 12:39 AM
Severity
Low
Public date
Aug 13, 2016, 12:00 AM