CVE-2017-3143: An error in TSIG authentication can permit unauthorized dynamic updates
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
Other sources
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. Affects BIND 9.4.0->9.8.8, 9.9.0->9.9.10-P1, 9.10.0->9.10.5-P1, 9.11.0->9.11.1-P1, 9.9.3-S1->9.9.10-S2, 9.10.5-S1->9.10.5-S2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/bind9to a version that resolves this vulnerability.Fixed in 1:9.11.5.P4+dfsg-5.1+deb10u7Fixed in 1:9.11.5.P4+dfsg-5.1+deb10u9Fixed in 1:9.16.44-1~deb11u1Fixed in 1:9.18.19-1~deb12u1Fixed in 1:9.19.17-1 - Upgrade
Upgrade
redhat/bindto a version that resolves this vulnerability.Fixed in 9.9.10 - Upgrade
Upgrade
redhat/bindto a version that resolves this vulnerability.Fixed in 9.10.5 - Upgrade
Upgrade
redhat/bindto a version that resolves this vulnerability.Fixed in 9.11.1 - Upgrade
Upgrade
BIND 9to a version that resolves this vulnerability.Fixed in 9.10.5-P2 - Upgrade
Upgrade
BIND 9to a version that resolves this vulnerability.Fixed in 9.10.5-S3 - Upgrade
Upgrade
BIND 9to a version that resolves this vulnerability.Fixed in 9.11.1-P2 - Upgrade
Upgrade
BIND 9to a version that resolves this vulnerability.Fixed in 9.9.10-P2 - Upgrade
Upgrade
BIND 9to a version that resolves this vulnerability.Fixed in 9.9.10-S3 - Configuration
Configure ACLs so dynamic updates require address-based validation and TSIG authentication in parallel.
BIND 9 authoritative DNS server Access Control Lists (ACLs) = Require both address range validation and TSIG authentication
Event History
Frequently Asked Questions
What is the severity of CVE-2017-3143?
CVE-2017-3143 has a severity rating of medium as it allows unauthorized dynamic DNS updates if exploited.
How do I fix CVE-2017-3143?
To fix CVE-2017-3143, upgrade to the recommended versions of BIND, such as 1:9.11.5.P4+dfsg-5.1+deb10u7 or 9.10.5 for Red Hat.
What systems are vulnerable to CVE-2017-3143?
CVE-2017-3143 affects various versions of BIND, particularly those from 9.4.0 up to 9.11.1 and specific Red Hat versions.
Can CVE-2017-3143 be exploited remotely?
Yes, CVE-2017-3143 can be exploited remotely by attackers who can send messages to the targeted DNS server.
Who is affected by CVE-2017-3143?
Administrators of DNS servers that use BIND versions indicated in the vulnerability report may be affected by CVE-2017-3143.