Bug 1609400 (CVE-2018-14373) - CVE-2018-14373 libtiff: NULL dereference in TIFFFindField in tif_dirinfo.c
Summary: CVE-2018-14373 libtiff: NULL dereference in TIFFFindField in tif_dirinfo.c
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2018-14373
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1609401 1609402 1609404 1609405
Blocks: 1609415
TreeView+ depends on / blocked
 
Reported: 2018-07-27 21:54 UTC by Laura Pardo
Modified: 2021-02-16 23:52 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-09 08:35:57 UTC
Embargoed:

Attachments (Terms of Use)

Description Laura Pardo 2018-07-27 21:54:33 UTC 
An issue was discovered in LibTIFF 4.0.9. In TIFFFindField in tif_dirinfo.c, the structure tif is being dereferenced without first checking that the structure is not empty and has the requested fields (tif_foundfield). In the call sequences following from the affected library functions (TIFFVGetField, TIFFVGetFieldDefaulted, TIFFVStripSize, TIFFScanlineSize, TIFFTileSize, TIFFGetFieldDefaulted, and TIFFGetField), this sanitization of the tif structure is never being done and, hence, using them with an invalid or empty tif structure will trigger a buffer overflow, leading to a crash.


References:
http://bugzilla.maptools.org/show_bug.cgi?id=2801
Comment 1 Laura Pardo 2018-07-27 21:55:06 UTC 
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1609402]


Created mingw-libtiff tracking bugs for this issue:

Affects: epel-7 [bug 1609404]
Affects: fedora-all [bug 1609401]
Comment 3 Riccardo Schirone 2018-08-09 08:35:57 UTC 
CVE rejected https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14373
Comment 4 Doran Moppert 2020-02-11 00:30:40 UTC 
Statement:

Red Hat Product Security determined that this flaw was not a security vulnerability. See the Bugzilla link for more details.
Note You need to log in before you can comment on or make changes to this bug.