Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Perltidy Project | Perltidy | <= 2016-03-02 |
Related Weaknesses (CWE)
References
- https://bugs.debian.org/862667Issue TrackingThird Party Advisory
- https://bugs.debian.org/862667Issue TrackingThird Party Advisory
FAQ
What is CVE-2016-10374?
CVE-2016-10374 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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...
How severe is CVE-2016-10374?
CVE-2016-10374 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2016-10374?
Check the references section above for vendor advisories and patch information. Affected products include: Perltidy Project Perltidy.