An attacker who is able to send and receive messages to an authoritative DNS server and who has knowledge of a valid TSIG key name for the zone and service being targeted may be able to manipulate BIND into accepting an unauthorized dynamic update. A server that relies solely on TSIG or SIG(0) keys with no other address-based ACL protection could be vulnerable to malicious zone content manipulation using this technique. Workarounds: The effects of this vulnerability can be mitigated by using Access Control Lists (ACLs) that require both address range validation and use of TSIG authentication in parallel. For information on how to configure this type of compound authentication control, please see: https://kb.isc.org/article/AA-00723/0/Using-Access-Control-Lists-ACLs-with-both-addresses-and-keys.html. Administrators who have made use of named.conf option "update-policy local;" should refer to the Administrator Reference Manual (ARM) for details of the automatic update policy that will be established and to assess whether or not this conveys any additional risk to their server. (Note that this option is not enabled by default). Upstream patch: https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=581c1526ab
Acknowledgments: Name: Internet Systems Consortium Upstream: Clement Berthaux (Synacktiv)
External References: https://kb.isc.org/article/AA-01503
Created bind tracking bugs for this issue: Affects: fedora-all [bug 1466609] Created bind99 tracking bugs for this issue: Affects: fedora-all [bug 1466610]
Mitigation: The effects of this vulnerability can be mitigated by using Access Control Lists (ACLs) that require both address range validation and use of TSIG authentication in parallel. For information on how to configure this type of compound authentication control, please see: https://kb.isc.org/article/AA-00723/0/Using-Access-Control-Lists-ACLs-with-both-addresses-and-keys.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2017:1680 https://access.redhat.com/errata/RHSA-2017:1680
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:1679 https://access.redhat.com/errata/RHSA-2017:1679