| Name | CVE-2018-5360 |
| Description | LibTIFF before 4.0.6 mishandles the reading of TIFF files, as demonstrated by a heap-based buffer over-read in the ReadTIFFImage function in coders/tiff.c in GraphicsMagick 1.3.27. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, 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 (security), bullseye | 4.2.0-1+deb11u5 | fixed |
| bookworm, bookworm (security) | 4.5.0-6+deb12u1 | fixed |
| sid, trixie | 4.5.1+git230720-5 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| tiff | source | (unstable) | 4.0.6-3 | | | |
| tiff3 | source | (unstable) | undetermined | | | |
Notes
[jessie] - tiff <no-dsa> (Minor issue, duplicate of CVE-2014-8127)
[wheezy] - tiff3 <postponed> (Minor issue, revisit once fixed upstream)
Issue demostrated in tiff via a vector through graphicsmagick, cf.
https://sourceforge.net/p/graphicsmagick/bugs/540/
Same issue as http://bugzilla.maptools.org/show_bug.cgi?id=2500 (CVE-2014-8127)
fixed as per 2016-10-25 (first release to ship the patch seems to be 4.0.7)
https://gitlab.com/libtiff/libtiff/commit/739dcd28a061738b317c1e9f91029d9cbc157159