Bug 165682 - CVE-2005-2458 gzip/zlib flaws
CVE-2005-2458 gzip/zlib flaws
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Don Howard
Brian Brock
: Security
Depends On:
Blocks: 143573
  Show dependency treegraph
Reported: 2005-08-11 07:52 EDT by Mark J. Cox
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2006-0191
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-01 12:56:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox 2005-08-11 07:52:31 EDT
+++ This bug was initially created as a clone of Bug #165679 +++

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 1 Mark J. Cox 2005-08-18 06:12:17 EDT
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 6 Red Hat Bugzilla 2006-02-01 12:56:09 EST
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.


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