| Name | CVE-2017-16232 |
| Description | LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| tiff (PTS) | bullseye | 4.2.0-1+deb11u5 | vulnerable |
| bullseye (security) | 4.2.0-1+deb11u7 | vulnerable |
| bookworm | 4.5.0-6+deb12u2 | vulnerable |
| bookworm (security) | 4.5.0-6+deb12u3 | vulnerable |
| trixie | 4.7.0-3 | vulnerable |
| trixie (security) | 4.7.0-3+deb13u1 | vulnerable |
| forky, sid | 4.7.1-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| tiff | source | (unstable) | (unfixed) | unimportant | | |
Notes
http://seclists.org/oss-sec/2017/q4/168
Related commit: https://gitlab.com/libtiff/libtiff/commit/25f9ffa56548c1846c4a1f19308b7f561f7b1ab0
This is actually only a partial fix, but upstream will not fix it completely.
The related commit is included in 4.0.9. The underlying memory-based DOS
would still be present.