BIND 9 Security Vulnerability Matrix - 9.10-S
  • 22 Oct 2018
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF

BIND 9 Security Vulnerability Matrix - 9.10-S

  • Dark
  • PDF

Article summary

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 Supported Preview 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 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 Supported Preview edition

# CVE Number Short Description
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
92 2017-3145 Improper fetch cleanup sequencing in the resolver can cause named to crash
91 2017-3143 An error in TSIG handling can permit unauthorized dynamic updates
90 2017-3142 An error in TSIG handling can permit unauthorized zone transfers
89 2017-3141 Windows service and uninstall paths are not quoted when BIND is installed
88 2017-3140 An error processing RPZ rules can cause named to loop endlessly after handling a query

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.10 Subscription edition

If you'd like more information on our product support or about our BIND Subscription edition, please visit

(EOL July 2018; final matrix update 2018-09-19)

ver/CVE 88 89 90 91 92 93 94 95 96 97 98
9.10.7-S1 + + +
9.10.6-S3 + +
9.10.6-S2 + + +
9.10.6-S1 + + + +
9.10.5-S3 + + + +
9.10.5-S2 + + + + + +
9.10.5-S1 + + + + + + + +