Linux Today: Linux News On Internet Time.

More on LinuxToday

Red Hat Security Advisory: Security problems in bind

Nov 11, 1999, 20:59 (0 Talkback[s])
(Other stories by Bill Nottingham)

Date: Thu, 11 Nov 1999 15:35:15 -0500
From: Bill Nottingham <<a href="">>

Red Hat, Inc. Security Advisory

Synopsis: Security problems in bind
Advisory ID: RHSA-1999:054-01
Issue date: 1999-11-11
Updated on: 1999-11-11
Keywords: bind named NXT solinger fdmax
Cross references:

1. Topic:

Several security vulnerabilities exist in the DNS server, 'bind'.

2. Relevant releases/architectures:

Red Hat Linux 4.x, all platforms
Red Hat Linux 5.x, all platforms
Red Hat Linux 6.x, all platforms

3. Problem description:

Various vulnerabilities exist in previous versions of bind:

- A bug in the processing of NXT records can theoretically allow a remote attacker to gain access to the DNS server as the user running bind (by default, root). This vulnerability does not affect the bind packages that shipped with Red Hat Linux 4.2 and Red Hat Linux 5.2.
- 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.

4. Solution:

For each RPM for your particular architecture, run:
rpm -Uvh
where filename is the name of the RPM.

5. Bug IDs fixed ( for more info):

6. Obsoleted by:

7. Conflicts with:

8. RPMs required:

Red Hat Linux 4.x:




Source packages:

Red Hat Linux 5.x:




Source packages:

Red Hat Linux 6.x:




Source packages:

9. Verification:

MD5 sum                           Package Name

85f36ee60d5399199afe7edf9ce18942 i386/bind-8.2.2_P3-0.4.2.i386.rpm
e98ff23ac5cdcd888043697f1db9e353 i386/bind-devel-8.2.2_P3-0.4.2.i386.rpm
287949831c6c61689a74b72e3e079c3b i386/bind-utils-8.2.2_P3-0.4.2.i386.rpm
2b62c4d7e7dee54ecb91fff5297c47b1 alpha/bind-8.2.2_P3-0.4.2.alpha.rpm
06d0fdcca32569dbdb5d3002c253747a alpha/bind-devel-8.2.2_P3-0.4.2.alpha.rpm
e49d10be181ad751924da9cc7c420b45 alpha/bind-utils-8.2.2_P3-0.4.2.alpha.rpm
71ae14362db69894d621bc1a83e1ce87 sparc/bind-8.2.2_P3-0.4.2.sparc.rpm
4c8d988b34242f92233a3aabe82c4849 sparc/bind-devel-8.2.2_P3-0.4.2.sparc.rpm
923af5f384cca91082d76acc29e622ec sparc/bind-utils-8.2.2_P3-0.4.2.sparc.rpm
8be7216693b2bfff239731687c75c7e9 SRPMS/bind-8.2.2_P3-0.4.2.src.rpm

43958baf4d3cdd6ff9739af76ea49247 i386/bind-8.2.2_P3-0.5.2.i386.rpm
40f7819efa41df675337a762a2fa951d i386/bind-devel-8.2.2_P3-0.5.2.i386.rpm
663b01244e07904cb20df7051a685c01 i386/bind-utils-8.2.2_P3-0.5.2.i386.rpm
ee8c6d9c6d58819846992346e0235b6a alpha/bind-8.2.2_P3-0.5.2.alpha.rpm
ba02b045f964c9a58968ecf144480499 alpha/bind-devel-8.2.2_P3-0.5.2.alpha.rpm
4d411e79d11bee31d2ca8251dc2c26af alpha/bind-utils-8.2.2_P3-0.5.2.alpha.rpm
78b95b741d02046796547f022e4673f1 sparc/bind-8.2.2_P3-0.5.2.sparc.rpm
400d7a123fbf03239eb8e928a90f0ae6 sparc/bind-devel-8.2.2_P3-0.5.2.sparc.rpm
b1209cdd8fa1fc5770bf66043c246706 sparc/bind-utils-8.2.2_P3-0.5.2.sparc.rpm
5a5e75d61ba6a8804864e4f00e327ec1 SRPMS/bind-8.2.2_P3-0.5.2.src.rpm

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:

You can verify each package with the following command:
rpm --checksig

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

10. References: