BIND 9 Security Vulnerability Matrix - 9.12
  • Updated on 16 Oct 2019
  • 4 minutes to read
  • Contributors
  • Print
  • Share
  • Dark
    Light

BIND 9 Security Vulnerability Matrix - 9.12

  • Print
  • Share
  • Dark
    Light

The BIND versions listed in this article are EOL
This BIND 9 Security Vulnerability Matrix is a record of vulnerabilities affecting the EOL BIND 9.10 branch during (or very shortly after) its lifetime. It is known to be affected by some vulnerabilities discovered after the EOL date (July 2018) 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 Knowledgebase 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 BIND
We recommend that you not use obsolete versions of any ISC software. It was updated for a reason.

Listing of Vulnerabilities affecting BIND 9.10

# CVE Number Short Description
106 2019-6471 A race condition when discarding malformed packets can cause BIND to exit with an assertion failure
105 2019-6469 BIND Supported Preview Edition can exit with an assertion failure if ECS is in use
104 2019-6468 BIND Supported Preview Edition can exit with an assertion failure if nxdomain-redirect is used
103 2019-6467 An error in the nxdomain redirect feature can cause BIND to exit with an INSIST assertion failure in query.c
102 2018-5743 Limiting simultaneous TCP clients is ineffective
101 2019-6465 Zone transfer controls for writable DLZ zones were not effective
100 2018-5745 An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys
99 2018-5744 A specially crafted packet can cause named to leak memory
98 2018-5741 Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation
97 2018-5740 A flaw in the "deny-answer-aliases" feature can cause an INSIST assertion failure in named
96 2018-5738 Some versions of BIND can improperly permit recursive query service to unauthorized clients
95 2018-5737 BIND 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
94 2018-5736 Multiple transfers of a zone in quick succession can cause an assertion failure in rbtdb.c
93 2018-5734 A malformed request can trigger an assertion failure in badcache.c
Why don't the reference numbers begin at 1?
To reduce confusion we preserve the reference number across all of our articles and tables; to reduce clutter we have pared down the entries to only those listed in the table for this branch.

BIND 9.12

(EOL May 2019; final matrix update 2019-06-19)

ver/CVE 93 94 95 96 97 98 99 100 101 102 103 104 105 106
9.12.4-P2
9.12.4-P1 +
9.12.4 + + +
9.12.3-P4 + + +
9.12.3-P1 + + + + + +
9.12.3 + + + + + +
9.12.2-P2 + + + + + +
9.12.2-P1 + + + + + + +
9.12.2 + + + + + + + +
9.12.1-P2 + + + + + + + + +
9.12.1 + + + + + + + + + + +
9.12.0 + + + + + + + + + + +
Was this article helpful?