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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2017-05-17T19:00:00Z
Updated: 2024-09-17T02:27:13.650Z
Reserved: 2017-05-17T00:00:00Z
Link: CVE-2016-10374
Vulnrichment
No data.
NVD
Status : Analyzed
Published: 2017-05-17T19:29:00.117
Modified: 2020-03-02T18:50:10.953
Link: CVE-2016-10374
Redhat