bind vulnerabilities (Alpaquita)
57 vulnerabilities.
-
bindAlpaquita Specific RPZ configurations and query patterns may result in an unexpected exit 7.5 High -
bindAlpaquita Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization 7.5 High -
bindAlpaquita Concurrent GSS-TSIG messages corrupt memory 8.1 High -
bindAlpaquita Amplified resource exhaustion in inbound message processing 7.5 High -
bindAlpaquita NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets 5.9 Medium -
bindAlpaquita Message parser retains every identical singleton RDATA, enabling wire-to-work amplification 5.3 Medium -
bindAlpaquita Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching 5.3 Medium -
bindAlpaquita Unauthenticated IXFR deltas are applied to the live zone before TSIG verification 6.5 Medium -
bindAlpaquita Validating resolver can abort while caching a mismatched NOQNAME proof 7.5 High -
bindAlpaquita named aborts on a TKEY query when the user configuration has no global options statement 7.5 High -
bindAlpaquita Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path 7.5 High -
bindAlpaquita SVCB AliasMode additional-data error leaks qpcache references 7.5 High -
bindAlpaquita Out-of-zone database nodes can become authoritative zone cuts 5.8 Medium -
bindAlpaquita Unauthenticated remote crash of named via a single DoH SIG(0) request 7.5 High -
bindAlpaquita checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof 5.9 Medium -
bindAlpaquita qpcache NOQNAME proof use-after-free crashes recursive resolver 5.9 Medium -
bindAlpaquita Remote assertion failure via 16-bit length truncation in `dns_ncache_add()` 7.5 High -
bindAlpaquita Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees 7.5 High -
bindAlpaquita DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field 8.6 High -
bindAlpaquita Unexpected exit in certain situations with NSEC and NSEC3 both present 7.5 High -
bindAlpaquita Record ordering based unexpected exit with CNAME or DNAME 7.5 High -
bindAlpaquita Cache poisoning possible with label count discrepancy, RRSIG, and wildcards 7.5 High -
bindAlpaquita Potential memory usage beyond configured limits 7.5 High -
bindAlpaquita Unnecessary validation of DNSSEC signed records 7.5 High -
bindAlpaquita Potential wildcard CNAME RPZ policy bypass 7.5 High -
bindAlpaquita Key Record using PRIVATEDNS algorithm may lead to unexpected exit 6.5 Medium -
bindAlpaquita Incorrect acceptance of NSEC3 records 6.8 Medium -
bindAlpaquita Unbounded resend loop in BIND 9 resolver 5.3 Medium -
bindAlpaquita SIG(0) validation during query flood may lead to undefined behavior 7.5 High -
bindAlpaquita Invalid handling of CLASS != IN 7.5 High -
bindAlpaquita Heap use-after-free vulnerability in BIND 9 DNS-over-HTTPS implementation 7.4 High -
bindAlpaquita Amplification vulnerabilities via self-pointed glue records 5.3 Medium -
bindAlpaquita BIND 9 server memory exhaustion during GSS-API TKEY negotiation 7.5 High -
bindAlpaquita A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass 5.4 Medium -
bindAlpaquita Authenticated query containing a TKEY record may cause named to terminate unexpectedly 6.5 Medium -
bindAlpaquita Memory leak in code preparing DNSSEC proofs of non-existence 7.5 High -
bindAlpaquita Excessive NSEC3 iterations cause high CPU load during insecure delegation validation 7.5 High -
bindAlpaquita Malformed BRID/HHIT records can cause named to terminate unexpectedly 7.5 High -
bindAlpaquita Resource exhaustion via malformed DNSKEY handling 7.5 High -
bindAlpaquita Cache poisoning due to weak PRNG 8.6 High -
bindAlpaquita Cache poisoning attacks with unsolicited RRs 8.6 High -
bindAlpaquita Birthday Attack against Resolvers supporting ECS 8.6 High -
bindAlpaquita A possible assertion failure when 'stale-answer-client-timeout' is set to '0' 7.5 High -
bindAlpaquita DNS message with invalid TSIG causes an assertion failure 7.5 High -
bindAlpaquita DNS-over-HTTPS implementation suffers from multiple issues under heavy query load 7.5 High -
bindAlpaquita Many records in the additional section cause CPU exhaustion 7.5 High -
bindAlpaquita Assertion failure when serving both stale cache data and authoritative zone content 7.5 High -
bindAlpaquita SIG(0) can be used to exhaust CPU resources 7.5 High -
bindAlpaquita BIND's database will be slow if a very large number of RRs exist at the same name 7.5 High -
bindAlpaquita A flood of DNS messages over TCP may make the server unstable 7.5 High - Show olderLoading…