Launchpad has imported 19 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=837577.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-07-04T10:01:43+00:00 Jan wrote: A heap-based buffer overflow flaw was found in the way tiff2pdf, a TIFF image to a PDF document conversion tool, of libtiff, a library of functions for manipulating TIFF (Tagged Image File Format) image format files, performed write of TIFF image content into particular PDF document file, when not properly initialized T2P context struct pointer has been provided by tiff2pdf (application requesting the conversion) as one of parameters for the routine performing the write. A remote attacker could provide a specially-crafted TIFF image format file, that when processed by tiff2pdf would lead to tiff2pdf executable crash or, potentially, arbitrary code execution with the privileges of the user running the tiff2pdf binary. Issue found by: Huzaifa Sidhpurwala, Red Hat Security Response Team Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/0 ------------------------------------------------------------------------ On 2012-07-18T15:13:42+00:00 Tom wrote: I have pushed the patches attached to this BZ into upstream libtiff CVS. They don't seem to have a cvsweb server, but instructions for anonymous CVS access are at http://www.remotesensing.org/libtiff/ Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/1 ------------------------------------------------------------------------ On 2012-07-19T02:51:59+00:00 Huzaifa wrote: This is now public via: http://seclists.org/oss-sec/2012/q3/88 Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/2 ------------------------------------------------------------------------ On 2012-07-19T06:52:37+00:00 mancha wrote: Hi. Do we have a similar situation at tools/tiff2pdf.c:3184? Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/4 ------------------------------------------------------------------------ On 2012-07-19T08:32:32+00:00 Huzaifa wrote: (In reply to comment #16) > This is now public via: > > http://seclists.org/oss-sec/2012/q3/88 The above link is wrong, correct link is: http://seclists.org/oss-sec/2012/q3/101 Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/5 ------------------------------------------------------------------------ On 2012-07-19T14:20:04+00:00 Tom wrote: (In reply to comment #18) > Hi. Do we have a similar situation at tools/tiff2pdf.c:3184? This question is pretty content-free, since I have no idea what version of the file you're looking at. How about quoting code instead of expecting me to guess? Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/7 ------------------------------------------------------------------------ On 2012-07-19T14:49:47+00:00 mancha wrote: (In reply to comment #21) > This question is pretty content-free, since I have no idea what version of > the file you're looking at. How about quoting code instead of expecting me > to guess? Taking my cues from your patch, I looked at v4.0.2. Below is the extract from t2p_process_ojpeg_tables() which I referred to: 3159 t2p->t2p_error = T2P_ERR_ERROR; 3160 return(0); 3161 } 3162 if(!TIFFGetField(input, TIFFTAG_JPEGPOINTTRANSFORM, &pt)){ 3163 TIFFError(TIFF2PDF_MODULE, 3164 "Missing JPEGPointTransform field in OJPEG image %s", 3165 TIFFFileName(input)); 3166 t2p->t2p_error = T2P_ERR_ERROR; 3167 return(0); 3168 } 3169 } 3170 if(!TIFFGetField(input, TIFFTAG_YCBCRSUBSAMPLING, &h_samp, &v_samp)){ 3171 h_samp=1; 3172 v_samp=1; 3173 } 3174 if(t2p->pdf_ojpegdata != NULL){ 3175 _TIFFfree(t2p->pdf_ojpegdata); 3176 t2p->pdf_ojpegdata=NULL; 3177 } 3178 t2p->pdf_ojpegdata = _TIFFmalloc(2048); 3179 if(t2p->pdf_ojpegdata == NULL){ 3180 TIFFError(TIFF2PDF_MODULE, 3181 "Can't allocate %u bytes of memory for t2p_process_ojpeg_tables, %s", 3182 2048, 3183 TIFFFileName(input)); 3184 return(0); 3185 } Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/8 ------------------------------------------------------------------------ On 2012-07-19T15:48:30+00:00 Tom wrote: Yeah, you're right, that should set t2p_error --- and looking through the file, I found a similar oversight in t2p_write_pdf(). These cases do not have any security content though, because AFAICS nothing will crash if pdf_ojpegdata (or pdf_xrefoffsets in the other place) is left null. You might get a bogus additional error message, and/or failure to exit(1) as desired, but no worse. I've pushed those fixes into upstream CVS, so they will be in the next releases, but I don't think they should be considered part of the CVE issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/9 ------------------------------------------------------------------------ On 2012-07-20T05:18:13+00:00 Huzaifa wrote: Created libtiff tracking bugs for this issue Affects: fedora-all [bug 841736] Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/10 ------------------------------------------------------------------------ On 2012-07-26T22:23:59+00:00 Fedora wrote: libtiff-3.9.6-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/11 ------------------------------------------------------------------------ On 2012-08-09T23:17:52+00:00 Fedora wrote: libtiff-3.9.6-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/13 ------------------------------------------------------------------------ On 2012-08-16T14:38:35+00:00 Jan wrote: This issue affects the versions of the libtiff package, as shipped with Red Hat Enterprise Linux 5 and 6. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/14 ------------------------------------------------------------------------ On 2012-08-29T14:38:09+00:00 Jan wrote: Statement: The Red Hat Security Response Team has rated this issue as having moderate security impact. A future libtiff package update may address this issue in Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/15 ------------------------------------------------------------------------ On 2012-10-03T04:23:33+00:00 Murray wrote: Acknowledgements: This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/16 ------------------------------------------------------------------------ On 2012-11-28T06:12:06+00:00 Huzaifa wrote: Created libtiff tracking bugs for this issue Affects: fedora-all [bug 880907] Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/17 ------------------------------------------------------------------------ On 2012-12-18T21:10:28+00:00 errata-xmlrpc wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/18 ------------------------------------------------------------------------ On 2012-12-31T03:23:46+00:00 Fedora wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/19 ------------------------------------------------------------------------ On 2012-12-31T03:25:55+00:00 Fedora wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/20 ------------------------------------------------------------------------ On 2013-01-12T00:27:14+00:00 Fedora wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/comments/21 ** Changed in: tiff (Fedora) Status: Unknown => Fix Released ** Changed in: tiff (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026438 Title: (CVE-2012-3401) libtiff (tiff2pdf): Heap-based buffer overflow due to improper initialization of T2P context struct pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1026438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
