ISC BIND any version

Off-by-one error in the inet_network function in libbind in ISC BIND 9.4.2 and earlier, as used in libc in FreeBSD 6.2 through 7.0-PRERELEASE, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted input that triggers memory corruption.

A second vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack

Heap use-after-free vulnerability in BIND 9 DNS-over-HTTPS implementation

named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to db.c and resolver.c.

BIND does not sufficiently limit the number of fetches performed when processing referrals

Buffer overread in statistics channel code

A vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack

named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion failure and daemon exit) via TKEY queries.

buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted query.

buffer.c in named in ISC BIND 9.x before 9.9.7-P3 and 9.10.x before 9.10.2-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) by creating a zone containing a malformed DNSSEC key and issuing a query for a name in that zone.

Windows service and uninstall paths are not quoted when BIND is installed

dnskeygen in BIND 8.2.4 and earlier, and dnssec-keygen in BIND 9.1.2 and earlier, set insecure permissions for a HMAC-MD5 shared secret key file used for DNS Transactional Signatures (TSIG), which allows attackers to obtain the keys and perform dynamic DNS updates.

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

A flaw in the "deny-answer-aliases" feature can cause an assertion failure in named

named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries

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 malformed response to an RTYPE ANY query.

named in ISC BIND 9.x before 9.9.9-P4, 9.10.x before 9.10.4-P4, and 9.11.x before 9.11.0-P1 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a DNAME record in the answer section of a response to a recursive query, related to db.c and resolver.c.

Improper fetch cleanup sequencing in the resolver can cause named to crash

An error in TSIG authentication can permit unauthorized dynamic updates

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

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

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

Limiting simultaneous TCP clients was ineffective

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

Destroying a TLS session early causes assertion failure

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 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

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