Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 128842 - CAN-2002-0029 bind resolver issues affect glibc
CAN-2002-0029 bind resolver issues affect glibc
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: glibc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
: Security
Depends On:
  Show dependency treegraph
Reported: 2004-07-30 09:55 EDT by Mark J. Cox
Modified: 2016-11-24 10:16 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-04 17:34:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:383 high SHIPPED_LIVE Important: glibc security update 2004-08-04 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2004-07-30 09:55:10 EDT
An audit of our glibc packages in Red Hat Enterprise Linux found a
potential flaw in the resolver which was part of a security update to
BIND 4 in November 2002.


glibc as provided by Red Hat Enterprise Linux 2.1 does not include
this patch.  We're investigating to see if this is actually an issue
for the glibc-2.2.4 as shipped in RHEL2.1 or is mitigated by other
changes, but will include the fix in the next update in any event.
Comment 2 Jakub Jelinek 2004-07-30 17:38:53 EDT
glibc-2.2.4-32.17 is in dist-2.1AS-errata-candidate.
Comment 3 Mark J. Cox 2004-08-04 17:34:51 EDT
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.


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