7.5 High
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:P/I:P/A:P
0.008 Low
EPSS
Percentile
81.9%
A vulnerability in BIND, repaired in verison 8.2.2p5, allows remote attackers to execute code with the privileges of the process running named. This vulnerability was widely exploited from November 1999 to December 2000.
There is a buffer overflow in the processing of NXT records in the routine rrextract, part of the file ns_resp.c. Specifically, in vulnerable versions of BIND, there is a section of code which reads:
case T_NXT:
n = dn_expand(msg, eom, cp, (char *)data, sizeof data);
if (n < 0) {
hp->rcode = FORMERR;
return (-1);
}
if (!ns_nameok((char *)data, class, NULL, response_trans,
domain_ctx, dname, from.sin_addr)) {
hp->rcode = FORMERR;
return (-1);
}
cp += n;
cp1 = data + strlen((char *)data) + 1;
memcpy(cp1, cp, dlen - n);
The value of the dlen can be influenced by an intruder in such a way that the expression ‘dlen - n’ is larger than the size allocated to cp1. Further, the contents of cp can be influenced by an intruder. Thus, this vulnerability can be exploited to execute arbitrary code with the privileges of the process running named.
An exploit for this vulnerability is publicly available .
NXT record processing was introduced to BIND in version 8.2. 8.1.2 and earlier (including 4.9.x) do not appear to be vulnerable to this problem.
Remote user may gain default process access of local nameserver, usually root
Upgrade to the latest version of BIND.
16532
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Updated: January 28, 2001
Affected
Santa Cruz Operation, Inc
Security patches for the following SCO products will
be made available at <http://www.sco.com/security>
UnixWare 7.x.x is also reported to be vulnerable
UnixWare 2.x.x is also reported to be vulnerable
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%2316532 Feedback>).
Updated: January 28, 2001
Not Affected
Regarding the BIND related vulnerabilities VU#16532/VU#13145/VU#4512, Fujitsu’s UXP/V operating system is not vulnerable.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%2316532 Feedback>).
Updated: January 28, 2001
Not Affected
After [] investigation, we have concluded that we are also not vulnerable to Vulnerability #2. Therefore please state that Sun is not vulnerable for both VU#16532 and VU#13145…
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%2316532 Feedback>).
Updated: January 28, 2001
Unknown
COMPAQ COMPUTER CORPORATION
-----------------------------
At the time of writing this document, Compaq is currently investigating
the potential impact to Compaq’s BIND release(s).
As further information becomes available Compaq will provide notice of the
completion/availability of any necessary patches through AES services (DIA,
DSNlink FLASH and posted to the Services WEB page) and be available from your
normal Compaq Services Support channel.
COMPAQ COMPUTER CORPORATION 9/99
----------------------------- ----
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%2316532 Feedback>).
Updated: January 28, 2001
Unknown
We are investigating. We will provide an update when our investigation is complete.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%2316532 Feedback>).
Group | Score | Vector |
---|---|---|
Base | ||
Temporal | ||
Environmental |
Our thanks to ISC for assistance in understanding this vulnerability.
This document was written by Shawn V Hernan.
CVE IDs: | CVE-1999-0833 |
---|---|
CERT Advisory: | CA-1999-14 Severity Metric: |