ISC BIND

ISC BIND 9.1.0 through 9.8.4-P2 and 9.9.0 through 9.9.2-P2 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via malformed options data in an OPT resource record.

named in ISC BIND 9.9.9-P4, 9.9.9-S6, 9.10.4-P4, and 9.11.0-P1 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a response containing an inconsistency among the DNSSEC-related RRsets.

named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries

An error in TSIG authentication can permit unauthorized dynamic updates

named in ISC BIND 9.x before 9.9.9-P5, 9.10.x before 9.10.4-P5, and 9.11.x before 9.11.0-P2 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted DS resource record in an answer.

Combination of DNS64 and RPZ Can Lead to Crash

named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota

Buffer overflow in the DNS resolver code used in libc, glibc, and libbind, as derived from ISC BIND, allows remote malicious DNS servers to cause a denial of service and possibly execute arbitrary code via the stub resolvers.

An UPDATE message flood may cause named to exhaust all available memory

Buffer overflow in named in BIND 4 versions 4.9.10 and earlier, and 8 versions 8.3.3 and earlier, allows remote attackers to execute arbitrary code via a certain DNS server response containing SIG resource records (RR).

BIND before 9.2.6-P1 and 9.3.x before 9.3.2-P1 allows remote attackers to cause a denial of service (crash) via certain SIG queries, which cause an assertion failure when multiple RRsets are returned.

An assertion check can fail while answering queries for DNAME records that require the DNAME to be processed to resolve itself

Some versions of BIND can improperly permit recursive query service to unauthorized clients

BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is not enabled.

Buffer overflows in the DNS stub resolver library in ISC BIND 4.9.2 through 4.9.10, and other derived libraries such as BSD libc and GNU glibc, allow remote attackers to execute arbitrary code via DNS server responses that trigger the overflow in the (1) getnetbyname, or (2) getnetbyaddr functions, aka "LIBRESOLV: buffer overrun" and a different vulnerability than CVE-2002-0684.

A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

BIND 4 (BIND4) and BIND 8 (BIND8), if used as a target forwarder, allows remote attackers to gain privileged access via a "Kashpureff-style DNS cache corruption" attack.

An error handling certain queries using the nxdomain-redirect feature could cause a REQUIRE assertion failure in db.c

Limiting simultaneous TCP clients was ineffective

A flaw in native PKCS#11 code can lead to a remotely triggerable assertion failure in pk11.c

A malformed request can trigger an assertion failure in badcache.c

Destroying a TLS session early causes assertion failure

Buffer overflow in DNS resolver functions that perform lookup of network names and addresses, as used in BIND 4.9.8 and ported to glibc 2.2.5 and earlier, allows remote malicious DNS servers to execute arbitrary code through a subroutine used by functions such as getnetbyname and getnetbyaddr.

An error in the nxdomain redirect feature can cause BIND to exit with an INSIST assertion failure in query.c

TCP-pipelined queries can bypass tcp-clients limit

named's configured cache size limit can be significantly exceeded

In BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3, An attacker who can establish a TCP connection with the server and send data on that connection can exploit this to trigger the assertion failure, causing the server to exit.

A too-strict assertion check could be triggered when responses in BIND 9.16.19 and 9.17.16 require UDP fragmentation if RRL is in use

A specially crafted packet can cause named to leak memory

Memory leak in ECDSA DNSSEC verification code

Memory leaks in EdDSA DNSSEC verification code

Attempting QNAME minimization after forwarding can lead to an assertion failure in resolver.c

An error in QNAME minimization code can cause BIND to exit with an assertion failure

A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly

BIND Supported Preview Edition can exit with an assertion failure if nxdomain-redirect is used

Internet Systems Consortium (ISC) BIND 9.6.0 and earlier does not properly check the return value from the OpenSSL EVP_VerifyFinal function, which allows remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077 and CVE-2009-0025.

Exceeding the recursive-clients quota may cause named to terminate unexpectedly when stale-answer-client-timeout is set to 0

BIND 9 server memory exhaustion during GSS-API TKEY negotiation

named may terminate unexpectedly under high DNS-over-TLS query load

Buffer overflow in BIND 8.2 via NXT records.