Bug 58506 - bind shipped with RH subject to TSIG buf overflow bug
Summary: bind shipped with RH subject to TSIG buf overflow bug
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind   
(Show other bugs)
Version: 7.0
Hardware: All Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2002-01-18 09:55 UTC by Landon Curt Noll
Modified: 2007-03-27 03:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-18 18:23:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Landon Curt Noll 2002-01-18 09:55:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-13custom i686)

Description of problem:
It is possible to overflow a buffer handling TSIG signed queries, thereby
obtaining access
to the system.

See: http://www.isc.org/products/BIND/bind-security.html

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

How reproducible:

Steps to Reproduce:
1.rpm -q bind

Actual Results:  bind version 8.2.3-1

Expected Results:  bind v8.2.5 or better

Additional info:

Exploits for this bug exist.

The vind shipped with RH7.0, RH7.1 and RH7.2 is vulerable.

Comment 1 Bernhard Rosenkraenzer 2002-01-18 18:23:32 UTC
Not quite.

7.1 shipped with bind 9.1.0
7.2 shipped with bind 9.1.3

7.0 is still at 8.2.3 though.

Comment 2 Bernhard Rosenkraenzer 2002-01-18 18:26:32 UTC
And (just checked) 8.2.3 does NOT have this bug. The last version with this
problem was 8.2.2p7, according to the page you mentioned yourself.

Comment 3 Landon Curt Noll 2002-01-18 18:58:13 UTC
The page does mention 8.2.3-betas, which is later than 8.2.2p7.

Is 8.2.3-1 based on one of the 8.2.3-betas?

Comment 4 Bernhard Rosenkraenzer 2002-01-18 19:00:35 UTC
No, it's based on 8.2.3-RELEASE.

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