Summary
This update for bind fixes the following issues:
- CVE-2024-1737: 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
adding a configurable limit to the number of records that can
be stored per name and type in a cache or zone database. The
default is 100, which can be tuned with the new
max-types-per-name option. (bsc#1228256)
- CVE-2024-1975: 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.
(bsc#1228257)
Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE HPC 15 SP2 Linux Enterprise High Performance Computing 15 SP2-LTSS | bind | 9.16.6-150000.12.77.1 |
| SUSE · SLES 15 SP2 Linux Enterprise Server 15 SP2-LTSS | bind | 9.16.6-150000.12.77.1 |
| SUSE · SLES for SAP 15 SP2 Linux Enterprise Server for SAP Applications 15 SP2 | bind | 9.16.6-150000.12.77.1 |
| SUSE · Manager Client Tools for SLE Micro 5 | bind | 9.16.6-150000.12.77.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…