The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade perltidy | Jul 30, 2024 | May 17, 2017 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Aug 13, 2016 |
| Ubuntu | — | No solution exists | Jun 26, 2025 | May 17, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub