Summary
This update for bind fixes the following issues:
- CVE-2022-3094: UPDATE message flood may cause `named` to exhaust all available memory (bsc#1207471).
- CVE-2026-3039: BIND 9 server memory exhaustion during GSS-API TKEY negotiation (bsc#1265591).
- CVE-2026-3592: amplification vulnerabilities via self-pointed glue records (bsc#1265592).
- CVE-2026-5946: invalid handling of `CLASS != IN` (bsc#1265594).
- CVE-2026-10723: incorrect acceptance of NSEC3 records (bsc#1271982).
- CVE-2026-11331: potential wildcard CNAME RPZ policy bypass (bsc#1271984).
- CVE-2026-11622: potential memory usage beyond configured limits (bsc#1271986).
- CVE-2026-11721: cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
- CVE-2026-13204: unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
- CVE-2026-13321: DNSSEC validation bypass via out-of-zone NSEC Next field (bsc#1271990).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · Manager Client Tools for SLE Micro 5 | bind | 9.16.6-150000.12.91.1 |
| SUSE · Multi Linux Manager Tools SLE-Micro-5 | bind | 9.16.6-150000.12.91.1 |
Vulnerabilities 10
-
High 8.6
DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field
The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1,…
-
High 7.5CVE-2022-3094 EPSS 13%
An UPDATE message flood may cause named to exhaust all available memory
Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the …
-
High 7.5
Potential wildcard CNAME RPZ policy bypass
An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It…
-
High 7.5
Potential memory usage beyond configured limits
A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage c…
-
High 7.5
Cache poisoning possible with label count discrepancy, RRSIG, and wildcards
It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker's zone, wh…
-
High 7.5
Unexpected exit in certain situations with NSEC and NSEC3 both present
If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.…
-
High 7.5
BIND 9 server memory exhaustion during GSS-API TKEY negotiation
BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integr…
-
High 7.5
Invalid handling of CLASS != IN
Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or `HESIOD`, or DNS messages that specify meta-classes (`ANY` or `NONE`) in the question section. Specially crafte…
-
Medium 6.8
Incorrect acceptance of NSEC3 records
BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through …
-
Medium 5.3
Amplification vulnerabilities via self-pointed glue records
BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone, the resolver will consume disproportionate resources. This issue affects BIND 9 versions 9.11.0 through 9.16.…
References
-
report
https://bugzilla.suse.com/1207471
-
report
https://bugzilla.suse.com/1265591
-
report
https://bugzilla.suse.com/1265592
-
report
https://bugzilla.suse.com/1265594
-
report
https://bugzilla.suse.com/1271982
-
report
https://bugzilla.suse.com/1271984
-
report
https://bugzilla.suse.com/1271986
-
report
https://bugzilla.suse.com/1271987
-
report
https://bugzilla.suse.com/1271989
-
report
https://bugzilla.suse.com/1271990
-
web
https://www.suse.com/security/cve/CVE-2022-3094
-
web
https://www.suse.com/security/cve/CVE-2026-10723
-
web
https://www.suse.com/security/cve/CVE-2026-11331
-
web
https://www.suse.com/security/cve/CVE-2026-11622
-
web
https://www.suse.com/security/cve/CVE-2026-11721
-
web
https://www.suse.com/security/cve/CVE-2026-13204
-
web
https://www.suse.com/security/cve/CVE-2026-13321
-
web
https://www.suse.com/security/cve/CVE-2026-3039
-
web
https://www.suse.com/security/cve/CVE-2026-3592
-
web
https://www.suse.com/security/cve/CVE-2026-5946