CVE-2016-10374 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 protecti...
MediumCVSS 5.5
EPSS 0.32%
- Published
- Updated
- Exploit status
- No public exploit known
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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/perltidy(Debian:12) | < 20140328-2 | 20140328-2 |
| debian/perltidy(Debian:13) | < 20140328-2 | 20140328-2 |
| debian/perltidy(Debian:14) | < 20140328-2 | 20140328-2 |
| perltidy project perltidy | <= 2016-03-02 | No fix listed |
References
- Debian Security Tracker CVE-2016-10374 vendor-advisory
- bugs.debian.org issue-tracking third-party-advisory