Improper fetch cleanup sequencing in the resolver can cause named to crashĪn error in TSIG handling can permit unauthorized dynamic updatesĪn error in TSIG handling can permit unauthorized zone transfers Multiple transfers of a zone in quick succession can cause an assertion failure in rbtdb.cĪ malformed request can trigger an assertion failure in badcache.c

Some versions of BIND can improperly permit recursive query service to unauthorized clientsīIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is not enabled Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentationĪ flaw in the 'deny-answer-aliases' feature can cause an INSIST assertion failure in named Listing of Vulnerabilities affecting BIND 9.9 # We recommend that you not use obsolete versions of any ISC software. This page explains our version numbering system.

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. See the matrix for current branches for more information about how to interpret these tables. If a vulnerability number is greater than the highest column heading, that branch has not been tested and should be assumed to be vulnerable. If a vulnerability number is less than the lowest column heading, that branch does not have any versions with it.

The second part is a table listing all of the releases in this branch along the side and vulnerabilities along the top.

The third column is a short description of the vulnerability, linked (where possible) to our Knowledgebase article on the vulnerability. The second column is the CVE (Common Vulnerabilities and Exposure) number for the vulnerability, linked to its page on.

The first column is a reference number for use in the tables in the second part. The first part is a table listing all of the vulnerabilities covered by this page.It is known to be affected by some vulnerabilities discovered after the EOL date (July 2018) but those will not be listed here. This BIND 9 Security Vulnerability Matrix is a record of vulnerabilities affecting the EOL BIND 9.9 branch during (or very shortly after) its lifetime.

269 m1 decrypted bindi