| Package | Affected versions | Patched versions |
|---|---|---|
| perltidy | ≤ 2016-03-02 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free