From marcdeslauriers@videotron.ca Sat Oct 23 17:11:24 2004
From: Marc Deslauriers
To: "bugtraq@securityfocus.com" ,
"full-disclosure@lists.netsys.com"
Date: Sat, 23 Oct 2004 07:28:43 -0400
Subject: [Full-Disclosure] [FLSA-2004:1947] Updated glibc packages fix flaws
-----------------------------------------------------------------------
Fedora Legacy Update Advisory
Synopsis: Updated glibc packages fix flaws
Advisory ID: FLSA:1947
Issue date: 2004-10-23
Product: Red Hat Linux
Keywords: Bugfix
Cross references: https://bugzilla.fedora.us/show_bug.cgi?id=1947
CVE Names: CAN-2002-0029
-----------------------------------------------------------------------
-----------------------------------------------------------------------
1. Topic:
Updated glibc packages that fix a security flaw in the resolver as well
as dlclose handling are now available.
The GNU libc packages (known as glibc) contain the standard C libraries
used by applications.
2. Relevant releases/architectures:
Red Hat Linux 7.3 - i386
3. Problem description:
A security audit of glibc revealed a flaw in the resolver library which
was originally reported as affecting versions of ISC BIND 4.9. This flaw
also applied to glibc versions before 2.3.2. An attacker who is able to
send DNS responses (perhaps by creating a malicious DNS server) could
remotely exploit this vulnerability to execute arbitrary code or cause a
denial of service. The Common Vulnerabilities and Exposures project
(cve.mitre.org) has assigned the name CAN-2002-0029 to this issue.
All users of glibc should upgrade to these updated packages, which
resolve these issues.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which
are not installed but included in the list will not be updated. Note
that you can also use wildcards (*.rpm) if your current directory *only*
contains the desired RPMs.
Please note that this update is also available via yum and apt. Many
people find this an easier way to apply updates. To use yum issue:
yum update
or to use apt:
apt-get update; apt-get upgrade
This will start an interactive process that will result in the
appropriate RPMs being upgraded on your system. This assumes that you
have yum or apt-get configured for obtaining Fedora Legacy content.
Please visit http://www fedoralegacy.org/docs for directions on how to
configure yum and apt-get.
5. Bug IDs fixed:
http://bugzilla.fedora.us - bug #1947
6. RPMs required:
Red Hat Linux 7.3:
SRPM:
http://download.fedoralegacy.org/redhat/7.3/updates/SRPMS/glibc-2.2.5-44.legacy.3.src.rpm
i386:
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-2.2.5-44.legacy.3.i686.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-common-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-debug-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-debug-2.2.5-44.legacy.3.i686.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-debug-static-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-devel-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-profile-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/glibc-utils-2.2.5-44.legacy.3.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/nscd-2.2.5-44.legacy.3.i386.rpm
7. Verification:
SHA1 sum Package Name
---------------------------------------------------------------------------
787b02c547d9578eab2112b681d58ce40589dd37
7.3/updates/i386/glibc-2.2.5-44.legacy.3.i386.rpm
d73f3bf9fd6c094dbf3d7c0409c0d34de40a1cfd
7.3/updates/i386/glibc-2.2.5-44.legacy.3.i686.rpm
df3fdb0f5d327b10bb285b06a5f1422642b980b7
7.3/updates/i386/glibc-common-2.2.5-44.legacy.3.i386.rpm
61e6c8521d67f38e96c679b3d263f6dccfb43b75
7.3/updates/i386/glibc-debug-2.2.5-44.legacy.3.i386.rpm
d5b070b85a0a57702f3259790e59707dd8d67ef1
7.3/updates/i386/glibc-debug-2.2.5-44.legacy.3.i686.rpm
e8988fb212ad671469f190f01b35c7664298ea58
7.3/updates/i386/glibc-debug-static-2.2.5-44.legacy.3.i386.rpm
f2043d369aeb8a8a39b0f1e429fdbcf08dcefd5b
7.3/updates/i386/glibc-devel-2.2.5-44.legacy.3.i386.rpm
5902d254f9926b0c532e8af5e0fe3ed22e105215
7.3/updates/i386/glibc-profile-2.2.5-44.legacy.3.i386.rpm
6c8b2d53b0626265c180ba09a1a6161e4be6765d
7.3/updates/i386/glibc-utils-2.2.5-44.legacy.3.i386.rpm
26282373e4cd3770b40b3cf10dc17b7f6f23ce6a
7.3/updates/i386/nscd-2.2.5-44.legacy.3.i386.rpm
b8f02cd099305c9866715493147ca9c9dcecfff0
7.3/updates/SRPMS/glibc-2.2.5-44.legacy.3.src.rpm
These packages are GPG signed by Fedora Legacy for security. Our key is
available from http://www.fedoralegacy org/about/security.php
You can verify each package with the following command:
rpm --checksig -v
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the sha1sum with the following command:
sha1sum
8. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0029
http://www.kb.cert.org/vuls/id/844360
9. Contact:
The Fedora Legacy security contact is . More
project details at http://www.fedoralegacy.org
---------------------------------------------------------------------
[ Part 2, "This is a digitally signed message part" ]
[ Application/PGP-SIGNATURE 196bytes. ]
[ Unable to print this part. ]