Several remote denial-of-service attacks are possible; by
using abnormal TCP options, causing the DNS server to use many
file descriptors, or using special SIG records, it may be possible
to crash the DNS server.
It is recommended that all users of bind upgrade to the latest
packages.
Thanks go to ISC for providing the updated packages.
3. Bug IDs fixed: (see bugzilla for more information)
4. Relevant releases/architectures:
Red Hat Linux 6.1, all architectures
5. Obsoleted by:
None
6. Conflicts with:
None
7. RPMs required:
Intel:
ftp://updates.Red Hat.com/6.1/i386/
bind-
8.2.2_P3-1.i386.rpm
bind-
devel-8.2.2_P3-1.i386.rpm
bind-
utils-8.2.2_P3-1.i386.rpm
Alpha:
ftp://updates.Red Hat.com/6.0/alpha
bind-
8.2.2_P3-1.alpha.rpm
bind-devel-8.2.2_P3-1.alpha.rpm
bind-utils-8.2.2_P3-1.alpha.rpm
SPARC:
ftp://updates.Red Hat.com/6.0/sparc
bind-
8.2.2_P3-1.sparc.rpm
bind-devel-8.2.2_P3-1.sparc.rpm
bind-utils-8.2.2_P3-1.sparc.rpm
Source:
ftp://updates.Red Hat.com/6.1/SRPMS
bind-
8.2.2_P3-1.src.rpm
8. Solution:
For each RPM for your particular architecture, run:
rpm -Uvh filename
where filename is the name of the RPM.
Then you will want to restart the named service like so:
/etc/rc.d/init.d/named stop
/etc/rc.d/init.d/named start
9. Verification:
MD5 sum Package Name
-------------------------------------------------------------------------
f0c2e341fe81310d3031be7e0d67225f i386/bind-8.2.2_P3-1.i386.rpm
4f34e526ec52c94b9cd3411892f920df i386/bind-devel-8.2.2_P3-1.i386.rpm
5cb10493b44f9fe2a9c6667ebe0a0a8f i386/bind-utils-8.2.2_P3-1.i386.rpm
94e19627ae83388e7d4795f45676c4b6 alpha/bind-8.2.2_P3-1.alpha.rpm
06932040ed8b8ff5eb8edb09c069acf9 alpha/bind-devel-8.2.2_P3-1.alpha.rpm
de0fa8d33d877d2ed7f8d26949b4a937 alpha/bind-utils-8.2.2_P3-1.alpha.rpm
54b757c6e240d4c82ca740ac49eb3db7 sparc/bind-8.2.2_P3-1.sparc.rpm
8453658392c3b2a321f7647eb875d5d2 sparc/bind-devel-8.2.2_P3-1.sparc.rpm
9894188ea1e8a5f657f13d940091114d sparc/bind-utils-8.2.2_P3-1.sparc.rpm
987d55828aab270e14777a034d029cea SRPMS/bind-8.2.2_P3-1.src.rpm
These packages are GPG signed by Red Hat, Inc. for security. Our key
is available at:
http://www.Red Hat.com/corp/contac
t.html
You can verify each package with the following command:
rpm --checksig filename
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
rpm --checksig --nogpg filename
Note that you need RPM >= 3.0 to check GnuPG keys.
10. References:
