Pedro Ribeiro discovered a use-after-free flaw in the t2p_readwrite_pdf_image() function in tiff2pdf, a tool for converting a TIFF image to a PDF document. A remote attacker could provide a specially-crafted TIFF file that, when processed by tiff2pdf, would cause tiff2pdf to crash or, potentially, execute arbitrary code with the privileges of the user running tiff2pdf. References: http://www.asmail.be/msg0055359936.html http://www.openwall.com/lists/oss-security/2013/08/08/6
Upstream bug: http://bugzilla.maptools.org/show_bug.cgi?id=2449 Proposed patch: http://bugzilla.maptools.org/attachment.cgi?id=513&action=diff
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 18 and Fedora 19.
This issue has been addressed upstream via the following cvs commit: revision 1.72 date: 2013-08-14 05:11:37 +0000; author: fwarmerdam; state: Exp; lines: +3 -2; commitid: MfRqD1oHXFa0En1x; ensure return after memory allocation failure (#2449, CVS-2013-4232)
Created libtiff tracking bugs for this issue: Affects: fedora-all [bug 996832]
Created mingw-libtiff tracking bugs for this issue: Affects: fedora-all [bug 996833]
libtiff-4.0.3-8.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
libtiff-4.0.3-8.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Huzaifa S. Sidhpurwala from comment #4) > This issue has been addressed upstream via the following cvs commit: > > revision 1.72 > date: 2013-08-14 05:11:37 +0000; author: fwarmerdam; state: Exp; lines: > +3 -2; commitid: MfRqD1oHXFa0En1x; > ensure return after memory allocation failure (#2449, CVS-2013-4232) This is very useful information, especially to people who maintain tiff in other distributions. It would be even more helpful if you would include the file or list of files since, with CVS, there's no quick way to find that information. Yes, you can grep for the commitid in the logs, but it's not like git, svn, or any other modern VCS where a changeset is a first-class object. Thanks! (I maintain tiff for debian and admit to often benefiting from the excellent work of RedHat people on identifying, patching, and backporting security issues.)
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2014:0223 https://rhn.redhat.com/errata/RHSA-2014-0223.html
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2014:0222 https://rhn.redhat.com/errata/RHSA-2014-0222.html
Statement: (none)