CWE
617
Advisory Published
Updated

CVE-2017-3138: named exits with a REQUIRE assertion failure if it receives a null command string on its control channel

First published: Sun Mar 12 2017(Updated: )

named contains a feature which allows operators to issue commands to a running server by communicating with the server process over a control channel, using a utility program such as rndc. A regression introduced in a recent feature change has created a situation under which some versions of named can be caused to exit with a REQUIRE assertion failure if they are sent a null command string. Affects BIND 9.9.9->9.9.9-P7, 9.9.10b1->9.9.10rc2, 9.10.4->9.10.4-P7, 9.10.5b1->9.10.5rc2, 9.11.0->9.11.0-P4, 9.11.1b1->9.11.1rc2, 9.9.9-S1->9.9.9-S9.

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
ISC BIND 9=9.9.9
ISC BIND 9=9.9.9-p1
ISC BIND 9=9.9.9-p2
ISC BIND 9=9.9.9-p3
ISC BIND 9=9.9.9-p4
ISC BIND 9=9.9.9-p5
ISC BIND 9=9.9.9-p6
ISC BIND 9=9.9.9-p7
ISC BIND 9=9.9.9-s1
ISC BIND 9=9.9.9-s7
ISC BIND 9=9.9.10-beta1
ISC BIND 9=9.9.10-rc1
ISC BIND 9=9.9.10-rc2
ISC BIND 9=9.10.4
ISC BIND 9=9.10.4-p1
ISC BIND 9=9.10.4-p2
ISC BIND 9=9.10.4-p3
ISC BIND 9=9.10.4-p4
ISC BIND 9=9.10.4-p5
ISC BIND 9=9.10.4-p6
ISC BIND 9=9.10.4-p7
ISC BIND 9=9.10.5-b1
ISC BIND 9=9.10.5-rc1
ISC BIND 9=9.10.5-rc2
ISC BIND 9=9.11.0
ISC BIND 9=9.11.0-p1
ISC BIND 9=9.11.0-p2
ISC BIND 9=9.11.0-p3
ISC BIND 9=9.11.0-p4
ISC BIND 9=9.11.1-b1
ISC BIND 9=9.11.1-rc1
ISC BIND 9=9.11.1-rc2
NetApp Data ONTAP
NetApp Element OS
NetApp OnCommand Balance
Debian=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.

Frequently Asked Questions

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

    CVE-2017-3138 is considered a medium severity vulnerability affecting BIND servers.

  • How do I fix CVE-2017-3138?

    To fix CVE-2017-3138, you should update your BIND software to the latest patched version.

  • Which versions of BIND are affected by CVE-2017-3138?

    CVE-2017-3138 affects several versions of BIND, including 9.9.9 and others listed in the vulnerability report.

  • Can CVE-2017-3138 be exploited remotely?

    Yes, CVE-2017-3138 can be exploited remotely under certain conditions.

  • What types of systems are impacted by CVE-2017-3138?

    CVE-2017-3138 impacts systems running affected versions of the BIND DNS software.

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