Bug 165679

Summary: CVE-2005-2458 gzip/zlib flaws
Product: Red Hat Enterprise Linux 4 Reporter: Mark J. Cox <mjc>
Component: kernelAssignee: Peter Staubach <staubach>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: medium    
Version: 4.0CC: jbaron
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,source=vendorsec
Fixed In Version: RHSA-2006-0101 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-17 08:32:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 168429    
Description Flags
Proposed patch none

Description Mark J. Cox 2005-08-11 11:45:49 UTC
Tim Yamin from Gentoo noticed that some older security related bugs in the
decompression code had not been fixed in the kernel.  This is fairly minor as
there are few places where the kernel decompresses arbitrary data.  However it
could be a problem for things like zisofs (if someone mounts a malicious
filesystem), perhaps cslip or ppp too).



Fix for 2.6 is here, pretty much identical for 2.4:


Comment 4 Mark J. Cox 2005-08-18 10:09:17 UTC
Sergey Vlasov has done some analysis on these issues and discovered that the
changes in file lib/zlib_inflate/inftrees.c are incorrect and in fact are not
needed.  Gentoo have agreed and therefore from the patch above please ignore the
lib/zlib_inflate/inftrees.c hunk.  This means that CAN-2005-2549 is dropped, but
CAN-2005-2548 still applies.

Comment 5 Jason Baron 2005-08-22 19:00:19 UTC
Marc, do CAN-2005-2458?

Comment 6 Jason Baron 2005-08-22 19:01:00 UTC
i meant Mark. sorry.

Comment 7 Peter Staubach 2005-10-20 17:51:54 UTC
Created attachment 120202 [details]
Proposed patch

Comment 12 Red Hat Bugzilla 2006-01-17 08:32:30 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.