CVE-2017-3136: An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;"

Published Mar 12, 2017
·
Updated

A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS64 feature and other preconditions were met.

Servers are at risk if they are configured to use DNS64 and if the option "break-dnssec yes;" is in use.

External References:

https://kb.isc.org/article/AA-01465

Mitigation:

Servers which have configurations which require DNS64 and "break-dnssec yes;" should upgrade. Servers which are not using these features in conjunction are not at risk from this defect.

Other sources

A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS64 feature and other preconditions were met. Affects BIND 9.8.0 -> 9.8.8-P1, 9.9.0 -> 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.0 -> 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0 -> 9.11.0-P3, 9.11.1b1->9.11.1rc1, 9.9.3-S1 -> 9.9.9-S8.

Affected Software

51 affected componentsFixes available
debian/bind9
1:9.11.5.P4+dfsg-5.1+deb10u71:9.11.5.P4+dfsg-5.1+deb10u91:9.16.44-1~deb11u11:9.18.19-1~deb12u11:9.19.17-1
redhat/bind<9.9.9
9.9.9
redhat/bind<9.10.4
9.10.4
redhat/bind<9.11.0
9.11.0
ISC BIND>=9.8.0<=9.8.8
ISC BIND>=9.9.0<=9.9.9
ISC BIND>=9.10.0<=9.10.4
ISC BIND=9.8.0-p1
ISC BIND=9.9.0-p1
ISC BIND=9.9.0-p2
ISC BIND=9.9.0-p3
ISC BIND=9.9.0-p4
ISC BIND=9.9.0-p5
ISC BIND=9.9.0-p6
ISC BIND=9.9.3
ISC BIND=9.9.3-s1
ISC BIND=9.9.10-beta1
ISC BIND=9.9.10-rc1
ISC BIND=9.10.4-p1
ISC BIND=9.10.4-p2
ISC BIND=9.10.4-p3
ISC BIND=9.10.4-p4
ISC BIND=9.10.4-p5
ISC BIND=9.10.4-p6
ISC BIND=9.10.5-b1
ISC BIND=9.10.5-rc1
ISC BIND=9.11.0
ISC BIND=9.11.0-p1
ISC BIND=9.11.0-p2
ISC BIND=9.11.0-p3
ISC BIND=9.11.1-beta1
ISC BIND=9.11.1-rc1
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.3
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Eus=7.3
redhat Enterprise Linux Server Eus=7.4
redhat Enterprise Linux Server Eus=7.5
redhat Enterprise Linux Server Eus=7.6
redhat Enterprise Linux Server Tus=7.3
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Workstation=6.0
redhat Enterprise Linux Workstation=7.0
NetApp Data Ontap Edge
NetApp Element Software
NetApp OnCommand Balance
Debian Debian Linux=8.0

Remediation

Information

Upgrade to the patched release most closely related to your current version of BIND. These can all be downloaded from http://www.isc.org/downloads. BIND 9 version 9.9.9-P8 BIND 9 version 9.10.4-P8 BIND 9 version 9.11.0-P5 BIND Supported Preview Edition is a special feature preview branch of BIND provided to eligible ISC support customers. BIND 9 version 9.9.9-S10 New maintenance releases of BIND are also scheduled which contain the fix for this vulnerability. In addition to the security releases listed above, fixes for this vulnerability are also included in these release candidate versions: BIND 9 version 9.9.10rc3 BIND 9 version 9.10.5rc3 BIND 9 version 9.11.1rc3

Event History

Apr 13, 2017
Data Sourced
04:33 AM
SeverityAffected Software
Jan 16, 2019
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
RemedyDescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-3136?

CVE-2017-3136 is classified as a critical denial-of-service vulnerability that can cause a server using DNS64 to crash.

2

How do I fix CVE-2017-3136?

To fix CVE-2017-3136, update your BIND software to a version that has patched the vulnerability, such as 1:9.11.5.P4+dfsg-5.1+deb10u7 or higher.

3

Which versions of BIND are affected by CVE-2017-3136?

CVE-2017-3136 affects various versions of BIND including, but not limited to, versions prior to 9.11.5.P4, 9.10.4, and 9.9.9.

4

What types of attacks can CVE-2017-3136 be exploited for?

CVE-2017-3136 can be exploited to carry out denial-of-service attacks against servers using the DNS64 feature, causing them to terminate unexpectedly.

5

Are there any specific environments where CVE-2017-3136 is a concern?

CVE-2017-3136 is particularly concerning for servers configured to use the DNS64 feature, commonly found in environments supporting IPv6.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203