ISC BIND 9.

Specific RPZ configurations and query patterns may result in an unexpected exit

• ISC BIND 9
• Denial of service

Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization

• ISC BIND 9
• Memory corruption
• Denial of service

Concurrent GSS-TSIG messages corrupt memory

• ISC BIND 9
• Race condition
• Memory corruption

Amplified resource exhaustion in inbound message processing

• ISC BIND 9
• Denial of service

NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets

• ISC BIND 9
• CWE-346

Message parser retains every identical singleton RDATA, enabling wire-to-work amplification

• ISC BIND 9
• CWE-405

Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching

• ISC BIND 9
• Denial of service

Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

• ISC BIND 9
• CWE-349

Validating resolver can abort while caching a mismatched NOQNAME proof

• ISC BIND 9
• Denial of service

named aborts on a TKEY query when the user configuration has no global options statement

• ISC BIND 9
• Denial of service

Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path

• ISC BIND 9
• Memory corruption

SVCB AliasMode additional-data error leaks qpcache references

• ISC BIND 9
• Denial of service

Out-of-zone database nodes can become authoritative zone cuts

• ISC BIND 9
• CWE-349

Unauthenticated remote crash of named via a single DoH SIG(0) request

• ISC BIND 9
• Memory corruption

checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof

• ISC BIND 9
• CWE-345

qpcache NOQNAME proof use-after-free crashes recursive resolver

• ISC BIND 9
• Memory corruption

Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`

• ISC BIND 9
• CWE-197

Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees

• ISC BIND 9
• CWE-1050

DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

• ISC BIND 9
• CWE-346

Unexpected exit in certain situations with NSEC and NSEC3 both present

• ISC BIND 9
• Denial of service

Record ordering based unexpected exit with CNAME or DNAME

• ISC BIND 9
• Denial of service

Cache poisoning possible with label count discrepancy, RRSIG, and wildcards

• ISC BIND 9
• CWE-1284

Potential memory usage beyond configured limits

• ISC BIND 9
• Denial of service

Unnecessary validation of DNSSEC signed records

• ISC BIND 9
• CWE-408

Potential wildcard CNAME RPZ policy bypass

• ISC BIND 9
• CWE-790

Key Record using PRIVATEDNS algorithm may lead to unexpected exit

• ISC BIND 9
• Denial of service
• CWE-1284

Incorrect acceptance of NSEC3 records

• ISC BIND 9
• Weak cryptography or TLS

Unbounded resend loop in BIND 9 resolver

• ISC BIND 9
• CWE-606

SIG(0) validation during query flood may lead to undefined behavior

• ISC BIND 9
• Race condition
• Memory corruption

Invalid handling of CLASS != IN

• ISC BIND 9
• Memory corruption
• Denial of service

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

• ISC BIND 9
• Memory corruption

Amplification vulnerabilities via self-pointed glue records

• ISC BIND 9
• CWE-408

BIND 9 server memory exhaustion during GSS-API TKEY negotiation

• ISC BIND 9
• Denial of service
• CWE-771

A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass

• ISC BIND 9
• CWE-305
• CWE-562

Authenticated query containing a TKEY record may cause named to terminate unexpectedly

• ISC BIND 9
• Denial of service

Memory leak in code preparing DNSSEC proofs of non-existence

• ISC BIND 9
• Denial of service

Excessive NSEC3 iterations cause high CPU load during insecure delegation validation

• ISC BIND 9
• Denial of service
• CWE-606

Malformed BRID/HHIT records can cause named to terminate unexpectedly

• ISC BIND 9
• Denial of service
• CWE-1286

Cache poisoning due to weak PRNG

• ISC BIND 9
• CWE-341

Cache poisoning attacks with unsolicited RRs

• ISC BIND 9
• CWE-349

Resource exhaustion via malformed DNSKEY handling

• ISC BIND 9
• CWE-405

A possible assertion failure when 'stale-answer-client-timeout' is set to '0'

• ISC BIND 9
• Denial of service

Birthday Attack against Resolvers supporting ECS

• ISC BIND 9
• CWE-349

DNS message with invalid TSIG causes an assertion failure

• ISC BIND 9
• CWE-232

DNS-over-HTTPS implementation suffers from multiple issues under heavy query load

• ISC BIND 9
• Denial of service

Many records in the additional section cause CPU exhaustion

• ISC BIND 9
• CWE-405

Assertion failure when serving both stale cache data and authoritative zone content

• ISC BIND 9
• Denial of service

SIG(0) can be used to exhaust CPU resources

• ISC BIND 9
• Denial of service

BIND's database will be slow if a very large number of RRs exist at the same name

• ISC BIND 9
• Denial of service

A flood of DNS messages over TCP may make the server unstable

• ISC BIND 9
• Denial of service

Specific recursive query patterns may lead to an out-of-memory condition

• ISC BIND 9
• Denial of service

Cleaning an ECS-enabled cache may cause excessive CPU load

• ISC BIND 9

Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution

• ISC BIND 9
• Denial of service

Querying RFC 1918 reverse zones may cause an assertion failure when "nxdomain-redirect" is enabled

• ISC BIND 9
• Denial of service

Parsing large DNS messages may cause excessive CPU load

• ISC BIND 9
• Denial of service

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

• ISC BIND 9

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

• ISC BIND 9
• CWE-1325

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

• ISC BIND 9

Malformed NSEC records can cause named to terminate unexpectedly when synth-from-dnssec is enabled

• ISC BIND 9

named's configured cache size limit can be significantly exceeded

• ISC BIND 9