The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) by the Internet Software Consortium (ISC). There is a format string vulnerability in BIND 4.9.4 that may allow remote intruders to gain access to systems running BIND. Although BIND 4.9.x is no longer officially maintained by ISC, various versions are still widely deployed on the Internet.
This vulnerability has been successfully exploited in a laboratory environment and presents a serious threat to the Internet infrastructure.
There is a format string vulnerability in the nslookupComplain() routine of several versions of ISC BIND. This vulnerability is reported to exist in all versions prior to BIND 4.9.5-P1.
This vulnerability may allow an attacker to execute privileged commands or code with the same permissions as the BIND server. Because BIND is typically run by a superuser account, the execution would occur with superuser privileges.
This vulnerability was patched by the ISC in an earlier version of BIND 4, most likely BIND 4.9.5-P1. However, there is strong evidence to suggest that some third party vendors who redistribute BIND have not included these changes in their BIND packages. Therefore, the CERT/CC recommends that all users of BIND 4 or its derivatives base their distributions on BIND 4.9.8.
The BIND 9.1 distribution can be downloaded from:
Please note that upgrading to BIND 4.9.8 also addresses the vulnerabilities discussed in VU#325431 and VU#572183.
Compaq Computer Corporation Affected
SuSE Inc. Affected
Sun Microsystems Inc. Affected
The SCO Group (SCO Linux) Affected
The SCO Group (SCO UnixWare) Affected
Apple Computer Inc. Not Affected
FreeBSD Not Affected
Hewlett-Packard Company Not Affected
MandrakeSoft Not Affected
Microsoft Corporation Not Affected
OpenBSD Not Affected
Data General Unknown
NEC Corporation Unknown
Red Hat Inc. Unknown
Siemens Nixdorf Unknown
Sony Corporation Unknown
The CERT/CC thanks the COVERT Labs at PGP Security for discovering and analyzing this vulnerability and the Internet Software Consortium for providing a patch to fix it.
This document was written by Jeffrey P. Lanza.