Linux ·
Ubuntu · Package update · February 8, 2019
Ubuntu · Package update · February 8, 2019libtiff-tools 4.0.9-5ubuntu0.2: libtiff-tools 4.0.9-5ubuntu0.2 for Ubuntu 18.04.6 LTS (bionic)
libtiff-tools 4.0.9-5ubuntu0.2, released February 8, 2019, fixes 6 CVEs in libtiff-tools. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.2483
97th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 1
Routine 5
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libtiff-tools | Ubuntu 18.04.6 LTS (bionic) | 4.0.9-5ubuntu0.2 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2018-12900 | libtiff: Fix DIVIDE_BY_ZERO in patch for (#1595579) | 8.8 | 0.2483 | None reported |
| Routine | CVE-2019-6128 | libtiff5: The TIFFFdOpen function in tif_unix.c in LibTIFF 4.0.10 has a memory leak, as demonstrated by pal2rgb. | n/a | 0.0385 | None reported |
| Routine | CVE-2018-19210 | libtiff5: In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that wi... | n/a | 0.0361 | None reported |
| Routine | CVE-2019-7663 | libtiff5: An Invalid Address dereference was discovered in TIFFWriteDirectoryTagTransferfunction in libtiff/tif_dirwrite.c in L... | n/a | 0.0336 | None reported |
| Routine | CVE-2018-17000 | libtiff5: A NULL pointer dereference in the function _TIFFmemcmp at tif_unix.c (called from TIFFWriteDirectoryTagTransferfuncti... | n/a | 0.0325 | None reported |
| Routine | CVE-2018-10779 | libtiff5: TIFFWriteScanline in tif_write.c in LibTIFF 3.8.2 has a heap-based buffer over-read, as demonstrated by bmp2tiff. | n/a | 0.0287 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.