Introduction
This document summarizes changes since BIND 9.10.4:
BIND 9.10.4-P6 addresses the security issue described in
CVE-2017-3135, and fixes a regression introduced in a prior
security release.
BIND 9.10.4-P5 addresses the security issues described in
CVE-2016-9131, CVE-2016-9147, CVE-2016-9444 and CVE-2016-9778.
BIND 9.10.4-P4 addresses the security issue described in
CVE-2016-8864.
BIND 9.10.4-P3 addresses the security issue described in
CVE-2016-2776 and addresses an interoperability issue with
ECS clients.
BIND 9.10.4-P2 addresses the security issue described in
CVE-2016-2775.
BIND 9.10.4-P1 addresses Windows installation issues, the %z
modifier is not supported under Windows and a race condition
in the rbt/rbtdb implementation resulting in named exiting
due to assertion failures being detected.
The latest versions of BIND 9 software can always be found at
http://www.isc.org/downloads/.
There you will find additional information about each release,
source code, and pre-compiled versions for Microsoft Windows
operating systems.
If a server is configured with a response policy zone (RPZ)
that rewrites an answer with local data, and is also configured
for DNS64 address mapping, a NULL pointer can be read
triggering a server crash. This flaw is disclosed in
CVE-2017-3135. [RT #44434]
named could mishandle authority sections
with missing RRSIGs, triggering an assertion failure. This
flaw is disclosed in CVE-2016-9444. [RT #43632]
named mishandled some responses where
covering RRSIG records were returned without the requested
data, resulting in an assertion failure. This flaw is
disclosed in CVE-2016-9147. [RT #43548]
named incorrectly tried to cache TKEY
records which could trigger an assertion failure when there was
a class mismatch. This flaw is disclosed in CVE-2016-9131.
[RT #43522]
It was possible to trigger assertions when processing
responses containing answers of type DNAME. This flaw is
disclosed in CVE-2016-8864. [RT #43465]
It was possible to trigger a assertion when rendering a
message using a specially crafted request. This flaw is
disclosed in CVE-2016-2776. [RT #43139]
Calling getrrsetbyname() with a non
absolute name could trigger an infinite recursion bug in
lwresd or named with
lwres configured if, when combined with
a search list entry from resolv.conf,
the resulting name is too long. This flaw is disclosed in
CVE-2016-2775. [RT #42694]
A synthesized CNAME record appearing in a response before the
associated DNAME could be cached, when it should not have been.
This was a regression introduced while addressing CVE-2016-8864.
[RT #44318]
Fixed a crash when calling rndc stats on some
Windows builds: some Visual Studio compilers generate code that
crashes when the "%z" printf() format specifier is used. [RT #42380]
ECS clients with the option set to 0.0.0.0/0/0 or ::/0/0
were incorrectly getting a FORMERR response.
Windows installs were failing due to triggering UAC without
the installation binary being signed.
A race condition in rbt/rbtdb was leading to INSISTs being
triggered.
Thank you to everyone who assisted us in making this release possible.
If you would like to contribute to ISC to assist us in continuing to
make quality open source software, please visit our donations page at
http://www.isc.org/donate/.
© 2001-2018 Internet Systems ConsortiumFor assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership.ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.
