First published: Fri Oct 28 2016(Updated: )
A defect in BIND's handling of responses containing a DNAME answer can cause a resolver to exit after encountering an assertion failure in db.c or resolver.c During processing of a recursive response that contains a DNAME record in the answer section, BIND can stop execution after encountering an assertion error in resolver.c (error message: "INSIST((valoptions & 0x0002U) != 0) failed") or db.c (error message: "REQUIRE(targetp != ((void *)0) && *targetp == ((void *)0)) failed"). A server encountering either of these error conditions will stop, resulting in denial of service to clients. The risk to authoritative servers is minimal; recursive servers are chiefly at risk.
Credit: cve@mitre.org
Affected Software | Affected Version | How 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.0.0<9.9.9 | |
ISC BIND 9 | >=9.10.0<9.10.4 | |
ISC BIND 9 | =9.9.9 | |
ISC BIND 9 | =9.9.9-beta1 | |
ISC BIND 9 | =9.9.9-beta2 | |
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.10.4 | |
ISC BIND 9 | =9.10.4-beta1 | |
ISC BIND 9 | =9.10.4-beta2 | |
ISC BIND 9 | =9.10.4-beta3 | |
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.11.0 | |
ISC BIND 9 | =9.11.0-alpha1 | |
ISC BIND 9 | =9.11.0-alpha2 | |
ISC BIND 9 | =9.11.0-alpha3 | |
ISC BIND 9 | =9.11.0-beta1 | |
ISC BIND 9 | =9.11.0-beta2 | |
ISC BIND 9 | =9.11.0-beta3 | |
NetApp Data ONTAP | ||
NetApp SolidFire & HCI Storage Node | ||
NetApp SteelStore Cloud Integrated Storage | ||
Red Hat Enterprise Linux Desktop | =5.0 | |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux Server EUS | =6.7 | |
Red Hat Enterprise Linux Server EUS | =7.2 | |
Red Hat Enterprise Linux Server EUS | =7.3 | |
Red Hat Enterprise Linux Server EUS | =7.4 | |
Red Hat Enterprise Linux Server EUS | =7.5 | |
Red Hat Enterprise Linux Server EUS | =7.6 | |
Red Hat Enterprise Linux Server EUS | =7.7 | |
Red Hat Enterprise Linux Server | =5.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =6.2 | |
Red Hat Enterprise Linux Server | =6.4 | |
Red Hat Enterprise Linux Server | =6.5 | |
Red Hat Enterprise Linux Server | =6.6 | |
Red Hat Enterprise Linux Server | =7.2 | |
Red Hat Enterprise Linux Server | =7.3 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.7 | |
Red Hat Enterprise Linux Server | =6.5 | |
Red Hat Enterprise Linux Server | =6.6 | |
Red Hat Enterprise Linux Server | =7.2 | |
Red Hat Enterprise Linux Server | =7.3 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.7 | |
Red Hat Enterprise Linux Workstation | =5.0 | |
Red Hat Enterprise Linux Workstation | =6.0 | |
Red Hat Enterprise Linux Workstation | =7.0 | |
Debian | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-8864 is considered high due to the potential for a resolver to terminate unexpectedly.
To fix CVE-2016-8864, upgrade to the latest version of BIND as specified in the vulnerability report.
CVE-2016-8864 affects various versions of BIND, specifically versions earlier than 9.11.0.
CVE-2016-8864 can cause BIND resolvers to crash, potentially leading to denial of service.
Currently, the only recommended solution for CVE-2016-8864 is to apply the provided patches or update to a fixed version of BIND.