Bug 860198 (CVE-2012-4447) - CVE-2012-4447 libtiff: Heap-buffer overflow when processing a TIFF image with PixarLog Compression
Summary: CVE-2012-4447 libtiff: Heap-buffer overflow when processing a TIFF image with...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2012-4447
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 880907 885308 885309 885310 885311 889443
Blocks: 859810
TreeView+ depends on / blocked
 
Reported: 2012-09-25 08:58 UTC by Huzaifa S. Sidhpurwala
Modified: 2019-09-29 12:55 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-21 08:59:54 UTC
Embargoed:

Attachments (Terms of Use)
Upstream patch (728 bytes, patch)
2012-09-25 09:07 UTC, Huzaifa S. Sidhpurwala 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1590 0 normal SHIPPED_LIVE Moderate: libtiff security update 2012-12-19 02:06:23 UTC

Description Huzaifa S. Sidhpurwala 2012-09-25 08:58:59 UTC 
A heap-based buffer overflow was found in the way libtiff, library for manipulating TIFF (Tagged Image File Format) image format files, processed certain TIFF images using PixarLog Compression format. An attacker could create a specially-crafted TIFF image that, when opened, could cause an application using libtiff to crash or, possibly, execute arbitrary code with the privileges of the user running the application.
Comment 2 Huzaifa S. Sidhpurwala 2012-09-25 09:01:45 UTC 
This issue was partly fixed in the libtiff-4.0.2 release via the following commit:

revision 1.37
date: 2012-05-24 23:21:45 +0000;  author: fwarmerdam;  state: Exp;  lines: +2 -2;  commitid: 5xHvb7ZoNW8P226w;
Allocate working buffer one word larger since we "forward accumulate" and overwrite the end by one word in at least some cases.


and later seems to be completely resolved in libtiff-4.0.3 via the following commit:

revision 1.38
date: 2012-06-21 01:01:53 +0000;  author: fwarmerdam;  state: Exp;  lines: +2 -2;  commitid: i91tq45sntOmJv9w;
make tbuf large enough for one stride past the end
Comment 3 Huzaifa S. Sidhpurwala 2012-09-25 09:05:09 UTC 
This issue affects the version of libtiff as shipped with Red Hat Enterprise Linux 5 and 6.

This issue affects the version of libtiff as shipped with Fedora 16 and Fedora 17.
Comment 4 Huzaifa S. Sidhpurwala 2012-09-25 09:07:03 UTC 
Created attachment 616925 [details]
Upstream patch
Comment 5 Huzaifa S. Sidhpurwala 2012-09-26 04:13:11 UTC 
This issue has been assigned CVE-2012-4447 as per:

http://seclists.org/oss-sec/2012/q3/563
Comment 8 Huzaifa S. Sidhpurwala 2012-11-28 06:11:44 UTC 
Created libtiff tracking bugs for this issue

Affects: fedora-all [bug 880907]
Comment 11 errata-xmlrpc 2012-12-18 21:10:34 UTC 
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2012:1590 https://rhn.redhat.com/errata/RHSA-2012-1590.html
Comment 12 Huzaifa S. Sidhpurwala 2012-12-21 08:55:55 UTC 
Created mingw-libtiff tracking bugs for this issue

Affects: fedora-all [bug 889443]
Comment 14 Fedora Update System 2012-12-31 03:23:59 UTC 
libtiff-3.9.7-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 15 Fedora Update System 2012-12-31 03:27:41 UTC 
libtiff-3.9.7-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 16 Fedora Update System 2013-01-12 00:27:30 UTC 
libtiff-4.0.3-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.