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.
References
Link | Resource |
---|---|
https://bugs.debian.org/862667 | Issue Tracking Third Party Advisory |
https://bugs.debian.org/862667 | Issue Tracking Third Party Advisory |
Configurations
History
21 Nov 2024, 02:43
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugs.debian.org/862667 - Issue Tracking, Third Party Advisory |
Information
Published : 2017-05-17 19:29
Updated : 2024-11-21 02:43
NVD link : CVE-2016-10374
Mitre link : CVE-2016-10374
CVE.ORG link : CVE-2016-10374
JSON object : View
Products Affected
perltidy_project
- perltidy
CWE
CWE-59
Improper Link Resolution Before File Access ('Link Following')