Bug 610776 (CVE-2010-2597) - CVE-2010-2597 libtiff: use of uninitialized values crash
Summary: CVE-2010-2597 libtiff: use of uninitialized values crash
Alias: CVE-2010-2597
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 583081 603703
TreeView+ depends on / blocked
Reported: 2010-07-02 12:20 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-07-08 16:01:46 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0519 0 normal SHIPPED_LIVE Important: libtiff security update 2010-07-08 15:34:41 UTC

Description Jan Lieskovsky 2010-07-02 12:20:42 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2010-2597 to
the following vulnerability:

The TIFFVStripSize function in tif_strip.c in LibTIFF 3.9.0 and 3.9.2
makes incorrect calls to the TIFFGetField function, which allows
remote attackers to cause a denial of service (application crash) via
a crafted TIFF image, related to "downsampled OJPEG input" and
possibly related to a compiler optimization that triggers a
divide-by-zero error.

  [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2597
  [2] http://bugzilla.maptools.org/show_bug.cgi?id=2215
  [3] https://bugs.launchpad.net/bugs/593067
  [4] https://bugzilla.redhat.com/show_bug.cgi?id=583081
  [5] https://bugzilla.redhat.com/show_bug.cgi?id=603703

Comment 1 Jan Lieskovsky 2010-07-02 12:23:10 UTC
This issue did NOT affect the version of the libtiff package,
as shipped with Red Hat Enterprise Linux 3.

This issue affects the versions of the libtiff package,
as shipped with Red Hat Enterprise Linux 4 and 5.


This issue does NOT affect the current versions of libtiff
and mingw32-libtiff packages, as shipped with Fedora releases of
12 and 13 (this flaws has been already addressed in those).

Comment 4 Tom Lane 2010-07-02 13:52:56 UTC
Actually, it's not so much a compiler optimization risk as use of uninitialized variables.  If the values happen to be zero to start with, you get a divide-by-zero.

Comment 5 errata-xmlrpc 2010-07-08 15:34:56 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 4
  Red Hat Enterprise Linux 5

Via RHSA-2010:0519 https://rhn.redhat.com/errata/RHSA-2010-0519.html

Note You need to log in before you can comment on or make changes to this bug.