Summary
This update for bind fixes the following issues:
Security issues fixed:
- It is possible to craft excessively large numbers of resource
record types for a given owner name, which has the effect of
slowing down database processing. This has been addressed by
only allowing a maximum of 100 records to be stored per name
and type in a cache or zone database. (CVE-2024-1737, bsc#1228256)
- Validating DNS messages signed using the SIG(0) protocol (RFC
2931) could cause excessive CPU load, leading to a
denial-of-service condition. Support for SIG(0) message
validation was removed from this version of named.
(CVE-2024-1975, bsc#1228257)
Fixed packages 3
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 SP5 Linux Enterprise Server 12 SP5 | bind | 9.11.22-3.57.1 |
| SUSE · SLES for SAP 12 SP5 Linux Enterprise Server for SAP Applications 12 SP5 | bind | 9.11.22-3.57.1 |
| SUSE · SLES 12 SP5 Linux Enterprise Software Development Kit 12 SP5 | bind | 9.11.22-3.57.1 |
Vulnerabilities 2
-
High 7.5
BIND's database will be slow if a very large number of RRs exist at the same name
Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE) can suffer from degraded performance as content is being added or updated, and also when handling client queries for this name. This iss…
-
High 7.5
SIG(0) can be used to exhaust CPU resources
If a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache, a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests. This issue aff…