| Name | CVE-2016-10374 |
| 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 862667 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| perltidy (PTS) | bullseye | 20200110-1 | fixed |
| bookworm | 20220613-1 | fixed | |
| sid, trixie | 20230309-2 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| perltidy | source | (unstable) | 20140328-2 | 862667 |
[jessie] - perltidy <no-dsa> (Minor issue; can be fixed via point release)
[wheezy] - perltidy <no-dsa> (Minor issue)