• Print
  • Share
  • Dark
    Light

BIND 9 Security Vulnerability Matrix - 9.2 Branch

  • Updated on 20 Sep 2018
  • 5 minutes to read
  • Contributors 

The BIND versions listed in this article are EOLThis BIND 9 Security Vulnerability Matrix is a record of vulnerabilities affecting the EOL BIND 9.2 branch during (or very shortly after) its lifetime. It is known to be affected by some vulnerabilities discovered after the EOL date (September 2007) but those will not be listed here.

This article has two parts

  • The first part is a table listing all of the vulnerabilities covered by this page. The first column is a reference number for use in the tables in the second part. The second column is the CVE (Common Vulnerabilities and Exposure) number for the vulnerability, linked to its page on cve.mitre.org. The third column is a short description of the vulnerability, linked (where possible) to our Knowledge Base article on the vulnerability.
  • The second part is a table listing all of the releases in this branch along the side and vulnerabilities along the top. If a vulnerability number is less than the lowest column heading, that branch does not have any versions with it. If a vulnerability number is greater than the highest column heading, that branch has not been tested and should be assumed to be vulnerable.

See the matrix for current branches for more information about how to interpret these tables.

We do not generally list alpha, beta or release candidate (RC) versions here, and recommend that you use only released software in any environment in which security could be an issue. This page explains our version numbering system.

Using obsolete versions of BINDWe recommend that you not use obsolete versions of any ISC software. It was updated for a reason.

Listing of Vulnerabilities affecting BIND 9.2

# CVE Number Short Description
44 2011-2465 Remote crash with certain RPZ configurations
43 2011-2464 remote packet denial of service against authoritative and recursive servers
42 2011-1910 Large RRSIG RRsets and negative caching can crash named
41 2011-1907 RRSIG queries can trigger server crash when using Response Policy Zones
40 2011-0414 Server lockup upon IXFR or DDNS update combined with high query rate
39 2010-3613 cache incorrectly allows an ncache entry and an RRSIG for the same type
38 2010-3615 allow-query processed incorrectly
37 2010-3614 Key algorithm rollover bug in BIND9
36 2010-3762 failure to handle bad signatures if multiple trust anchors configured
35 2010-0218 Unexpected ACL Behavior in BIND 9.7.2
34 2010-0213 RRSIG query handling bug in BIND 9.7.1
33 2010-0097 DNSSECvalidation code could cause bogus NXDOMAIN responses
32 2009-4022 Cache Update From Additional Section
31 2009-0696 Dynamic Update DoS attack
30 2008-5077 DNSSECissue with DSA and NSEC3DSA algorithms
29 2008-1447 DNScache poisoning issue
28 2008-0122 inet_network() off-by-one buffer overflow
27 2007-2930 cryptographically weak query ids (BIND8)
26 2007-2926 cryptographically weak query ids
25 2007-2925 allow-query-cache/allow-recursion default acls not set.
24 2007-2241 Sequence of queries can cause a recursive nameserver to exit.
23 2007-0494 Denial of service via ANY query response containing multiple RRsets.
22 2007-0493 Denial of service via unspecified vectors that cause "dereference a freed fetch context."
13 2002-0400 DoS internal consistency check (DoS_findtype)

Why don't the reference numbers begin at 1?In order to reduce confusion we preserve the reference number across all of our articles and tables. In order to reduce clutter we have pared down the entries to only those listed in the table for this branch.

BIND 9.2

(EOL September 2007; Final matrix update 2011-09-09)

ver/CVE 13 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
9.2.8-P1 + + + + + + + +
9.2.8 + + + + + + + + +
9.2.7 + + + + + + + + + + +
9.2.6 + + + + + + + + + + +
9.2.5 + + + + + + + + + + +
9.2.4 + + + + + + + + + + +
9.2.3 + + + + + + + + + + +
9.2.2 + + + + + + + + + + +
9.2.1 + + + + + + + + + + +
9.2.0 + + + + + + + + + + + +
Problems with this site? Email us at marketing@isc.org