2012.07.14

DATE	CVE	VULNERABILITY TITLE	RISK
2017-05-17	CVE-2016-10374	Link Following vulnerability in Perltidy Project Perltidy 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. local low complexity perltidy-project CWE-59	2.1