high
7.5
CWE
617
Advisory Published
CVE Published
Updated

CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

First published: Sun Mar 12 2017(Updated: )

Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. A server which is performing recursion can be forced to exit with an assertion failure if it can be caused to receive a response containing CNAME or DNAME resource records with certain ordering. An attacker can cause a denial of service by exploiting this condition. Recursive resolvers are at highest risk but authoritative servers are theoretically vulnerable if they perform recursion. External References: <a href="https://kb.isc.org/article/AA-01466">https://kb.isc.org/article/AA-01466</a>

Credit: security-officer@isc.org

Affected SoftwareAffected VersionHow to fix
debian/bind9
1:9.11.5.P4+dfsg-5.1+deb10u7
1:9.11.5.P4+dfsg-5.1+deb10u9
1:9.16.44-1~deb11u1
1:9.18.19-1~deb12u1
1:9.19.17-1
debian/1:9.8.4.dfsg.P1-6+nmu2+deb7u18<=undefined
debian/bind9<=1:9.9.5.dfsg-9+deb8u10<=1:9.9.5.dfsg-9
1:9.10.3.dfsg.P4-12.3
1:9.10.6+dfsg-1
1:9.9.5.dfsg-9+deb8u11
redhat/bind<9.9.9
9.9.9
redhat/bind<9.10.4
9.10.4
redhat/bind<9.11.0
9.11.0
BIND 9=9.9.9-p6
BIND 9=9.9.9-s8
BIND 9=9.9.10-beta1
BIND 9=9.9.10-rc1
BIND 9=9.10.4-p6
BIND 9=9.10.5-b1
BIND 9=9.10.5-rc1
BIND 9=9.11.0-p3
BIND 9=9.11.1-b1
BIND 9=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=6.2
redhat enterprise Linux server aus=6.4
redhat enterprise Linux server aus=6.5
redhat enterprise Linux server aus=6.6
redhat enterprise Linux server aus=7.2
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=6.7
redhat enterprise Linux server eus=7.2
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=6.5
redhat enterprise Linux server tus=6.6
redhat enterprise Linux server tus=7.2
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 GNU/Linux=8.0

Remedy

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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-3137?

    CVE-2017-3137 is classified as a high-severity vulnerability due to its potential to cause assertion failures leading to denial-of-service.

  • How do I fix CVE-2017-3137?

    To fix CVE-2017-3137, upgrade to a patched version of BIND specified in the remediation section, such as 9.11.5.P4+dfsg-5.1+deb10u7 or later.

  • What systems are affected by CVE-2017-3137?

    CVE-2017-3137 affects various versions of the BIND DNS server, particularly those below the patched versions mentioned in the remediation section.

  • What impact does CVE-2017-3137 have on my server?

    The impact of CVE-2017-3137 is that it may cause your server to crash or become unresponsive due to assertion failures when processing DNS responses.

  • Is there a workaround for CVE-2017-3137?

    There is no known workaround for CVE-2017-3137, so upgrading to a secure version is the recommended action.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203