CVE-2017-3142: An error in TSIG authentication can permit unauthorized zone transfers
  • 12 Nov 2018
  • 3 Minutes to read
  • Contributors
  • Dark
  • PDF

CVE-2017-3142: An error in TSIG authentication can permit unauthorized zone transfers

  • Dark
  • PDF

Article summary

An attacker may be able to circumvent TSIG authentication of AXFR and NOTIFY requests.

CVE: CVE-2017-3142

Document version: 2.0

Posting date: 29 June 2017

Program impacted: BIND

Versions affected: 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

Severity: Medium

Exploitable: Remotely


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, may be able to circumvent TSIG authentication of AXFR requests via a carefully constructed request packet. A server that relies solely on TSIG keys for protection with no other ACL protection could be manipulated into:

  • providing an AXFR of a zone to an unauthorized recipient, and/or
  • accepting bogus NOTIFY packets.


  • An unauthorized AXFR (full zone transfer) permits an attacker to view the entire contents of a zone. Protection of zone contents is often a commercial or business requirement.
  • If accepted, a NOTIFY sets the zone refresh interval to 'now'. If there is not already a refresh cycle in progress then named will initiate one by asking for the SOA RR from its list of masters. If there is already a refresh cycle in progress, then named will queue the new refresh request. If there is already a queued refresh request, the new NOTIFY will be discarded. Bogus notifications cannot be used to force a zone transfer from a malicious server, but could trigger a high rate of zone refresh cycles.

CVSS Score: 5.3


For more information on the Common Vulnerability Scoring System and to obtain your specific environmental score please visit:


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. For information on how to configure this type of compound authentication control, please see: Using Access Control Lists (ACLs) with both addresses and keys. (Note that this technique may not be effective against bogus NOTIFY packets if an attacker is able to reach the target DNS server while using a spoofed sending address).

Active exploits:

No known active exploits, but a similar issue was announced publicly on 23 June 2017 by another DNS server software provider.

Solution: Upgrade to the patched release most closely related to your current version of BIND. These can all be downloaded from

  • BIND 9 version 9.9.10-P2
  • BIND 9 version 9.10.5-P2
  • BIND 9 version 9.11.1-P2

BIND Supported Preview Edition is a special feature preview branch of BIND provided to eligible ISC support customers.

  • BIND 9 version 9.9.10-S3
  • BIND 9 version 9.10.5-S3

Acknowledgements: ISC would like to thank Clément Berthaux from Synacktiv for reporting this issue.

Document Revision History:

1.0 Advance Notification, 26 June 2017 1.1 Correct Notify to NOTIFY; Update phrasing in Workarounds section; Update phrasing in Description; Correct date of similar public announcement, 29 June 2017 2.0 Public disclosure, 29 June 2017

Related Documents:

See our BIND 9 Security Vulnerability Matrix for a complete listing of Security Vulnerabilities and versions affected.

Do you still have questions? Questions regarding this advisory should go to security-officer@isc.orgTo report a new issue, please encrypt your message using's PGP key which can be found here:  If you are unable to use encrypted email, you may also report new issues at:


ISC patches only currently supported versions. When possible we indicate EOL versions affected.  (For current information on which versions are actively supported, please see 

ISC Security Vulnerability Disclosure Policy:

Details of our current security advisory policy and practice can be found in the ISC Software Defect and Security Vulnerability Disclosure Policy.

This Knowledgebase article is the complete and official security advisory document.

Legal Disclaimer:

Internet Systems Consortium (ISC) is providing this notice on an "AS IS" basis. No warranty or guarantee of any kind is expressed in this notice and none should be implied. ISC expressly excludes and disclaims any warranties regarding this notice or materials referred to in this notice, including, without limitation, any implied warranty of merchantability, fitness for a particular purpose, absence of hidden defects, or of non-infringement. Your use or reliance on this notice or materials referred to in this notice is at your own risk. ISC may change this notice at any time.  A stand-alone copy or paraphrase of the text of this document that omits the document URL is an uncontrolled copy. Uncontrolled copies may lack important information, be out of date, or contain factual errors.