Bug 134847 - CAN-2004-0803 buffer overflows in libtiff
Summary: CAN-2004-0803 buffer overflows in libtiff
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: libtiff
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-06 18:45 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-22 15:00:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch for this issue. (1.99 KB, patch)
2004-10-06 18:49 UTC, Josh Bressers 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:577 0 high SHIPPED_LIVE Important: libtiff security update 2004-10-22 04:00:00 UTC

Description Josh Bressers 2004-10-06 18:45:01 UTC 
Chris Evans reported to vendor-sec multiple buffer overflows in
libtiff.  These issues could potentially lead to arbitrary code
execution from a malicious tiff image.

This issue also affects RHEL2.1

This issue has been embargoed until Oct 13.
Comment 1 Josh Bressers 2004-10-06 18:49:42 UTC 
Created attachment 104851 [details]
Proposed patch for this issue.
Comment 2 Matthias Clasen 2004-10-13 15:34:16 UTC 
Fixes are in 3.5.5-17 (RHEL2.1) and 3.5.7-20.1 (RHEL3)
Comment 3 Josh Bressers 2004-10-13 20:15:29 UTC 
lifting embargo
Comment 4 Josh Bressers 2004-10-22 15:00:37 UTC 
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2004-577.html
Note You need to log in before you can comment on or make changes to this bug.