Bug 86023 - Remote DOS on Bind 9.2.1
Remote DOS on Bind 9.2.1
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
: Security
Depends On:
  Show dependency treegraph
Reported: 2003-03-12 11:06 EST by Cory Jaeger
Modified: 2007-03-27 00:01 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-13 08:12:32 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 Cory Jaeger 2003-03-12 11:06:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207

Description of problem:
On our DNS server, bind v9.2.1 is easily crashed by running the Nessus
vulnerability scanner with all tests (not only safe tests) selected.  In
testing, the named service crashed consistently each time it was tested.  The
service would either crash immediately or within 30 seconds.

After downloading, compiling and installing BIND v9.2.2, the service no longer
crashes.  An upgrade RPM should be fairly trivial to produce.  When configured
and compiled with options matching the Red Hat 8.0 directory tree, I was able to
upgrade without any changes to my BIND configuration.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Download and install the Nessus vulnerability scanner (nessus.org)
2. Run named v9.2.1 on RH8 (possibly other versions)
3. Run Nessus and select ALL tests
4. Select the IP of the DNS server and scan

Actual Results:  Named service crashes within 30 seconds.

Expected Results:  Nothing

Additional info:
Comment 1 Daniel Walsh 2003-03-13 08:12:32 EST
The bind-9.2.2 package is done but it is being held up from going to rawhide,
because of some unrelated problems.


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