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