Bug 189974 - CVE-2006-2120 libtiff DoS
Summary: CVE-2006-2120 libtiff DoS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: libtiff
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard: source=vendorsec,reported=20060426,pu...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-26 12:14 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version: RHSA-2006-0425
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-09 11:32:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch extracted from upstream CVS (953 bytes, patch)
2006-04-26 12:14 UTC, Josh Bressers
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0425 0 normal SHIPPED_LIVE Important: libtiff security update 2006-05-09 04:00:00 UTC

Description Josh Bressers 2006-04-26 12:14:54 UTC
A bug was fixed upstream where a malformed tiff image can cause libtiff to crash
due to an OOB memory read.

http://bugzilla.remotesensing.org/show_bug.cgi?id=1065

Comment 1 Josh Bressers 2006-04-26 12:14:54 UTC
Created attachment 128248 [details]
Patch extracted from upstream CVS

Comment 2 Josh Bressers 2006-04-26 12:16:33 UTC
It's likely this issue affect RHEL2 and RHEL3 (I've not had time to check source
yet).

Comment 3 Matthias Clasen 2006-04-26 13:16:31 UTC
only affects RHEL4, tif_color.c is new in 3.6

Comment 6 Red Hat Bugzilla 2006-05-09 11:32:55 UTC
An advisory 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-2006-0425.html



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