| Name | CVE-2017-9404 |
| Description | In LibTIFF 4.0.7, a memory leak vulnerability was found in the function OJPEGReadHeaderInfoSecTablesQTable in tif_ojpeg.c, which allows attackers to cause a denial of service via a crafted file. |
| 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) |
| References | DLA-983-1, DLA-984-1 |
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 | fixed |
| bullseye (security) | 4.2.0-1+deb11u7 | fixed |
| bookworm | 4.5.0-6+deb12u2 | fixed |
| bookworm (security) | 4.5.0-6+deb12u3 | fixed |
| trixie (security), trixie | 4.7.0-3+deb13u1 | fixed |
| forky, sid | 4.7.1-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| tiff | source | wheezy | 4.0.2-6+deb7u14 | | DLA-984-1 | |
| tiff | source | jessie | 4.0.3-12.3+deb8u4 | | | |
| tiff | source | (unstable) | 4.0.8-1 | | | |
| tiff3 | source | wheezy | 3.9.6-11+deb7u6 | | DLA-983-1 | |
| tiff3 | source | (unstable) | (unfixed) | | | |
Notes
http://bugzilla.maptools.org/show_bug.cgi?id=2688
Fixed by: https://github.com/vadz/libtiff/commit/2ea32f7372b65c24b2816f11c04bf59b5090d05b
Possibly sensible to add the other memory leaks fixes in OJPEGReadHeaderInfoSecTables
method from tif_ojpeg.c, i.e.:
https://github.com/vadz/libtiff/commit/e9bd1b06fe25219cf0873fca70e46f01843fd9f4
https://github.com/vadz/libtiff/commit/8283e4d1b7e53340684d12932880cbcbaf23a8c1
Reproducing the issue itself is "covered" after fixing https://github.com/vadz/libtiff/commit/5ed9fea523316c2f5cec4d393e4d5d671c2dbc33
To verify 2ea32f7372b65c24b2816f11c04bf59b5090d05b fixes the issue build src:tiff
with ASAN with 5ed9fea523316c2f5cec4d393e4d5d671c2dbc33 reverted. Before the
2ea32f7372b65c24b2816f11c04bf59b5090d05b commit the Direct leak of 73 byte
with backtrace following the methods in http://bugzilla.maptools.org/show_bug.cgi?id=2688
is shown.