rpm package
almalinux/bind-devel
pkg:rpm/almalinux/bind-devel
Vulnerabilities (35)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-13321 | Hig | 8.6 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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, and 9.20.9-S1 throug | |
| CVE-2026-13204 | Hig | 7.5 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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.11.0 through 9.18.50, | |
| CVE-2026-11721 | Hig | 7.5 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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, which can result in cac | |
| CVE-2026-11622 | Hig | 7.5 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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 can be orders of magni | |
| CVE-2026-11331 | Hig | 7.5 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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 also may lead to an | |
| CVE-2026-10723 | Med | 6.8 | < 32:9.16.23-40.el9_8.8 | 32:9.16.23-40.el9_8.8 | Jul 22, 2026 | 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 9.18.50-S1, and 9.20. | |
| CVE-2026-5946 | Hig | 7.5 | < 32:9.18.33-15.el10_2.2 | 32:9.18.33-15.el10_2.2 | May 20, 2026 | 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 crafted requests reaching t | |
| CVE-2026-3039 | Hig | 7.5 | < 32:9.18.33-15.el10_2.2 | 32:9.18.33-15.el10_2.2 | May 20, 2026 | 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 integrated DNS deployments | |
| CVE-2026-1519 | Hig | 7.5 | < 32:9.16.23-34.el9_7.2 | 32:9.16.23-34.el9_7.2 | Mar 25, 2026 | If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see: | |
| CVE-2025-8677 | Hig | 7.5 | < 32:9.18.33-10.el10_1.2 | 32:9.18.33-10.el10_1.2 | Oct 22, 2025 | Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion. This issue affects BIND 9 versions 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 thr | |
| CVE-2025-40780 | Hig | 8.6 | < 32:9.18.33-10.el10_1.2 | 32:9.18.33-10.el10_1.2 | Oct 22, 2025 | In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9. | |
| CVE-2025-40778 | Hig | 8.6 | < 32:9.11.36-16.el8_10.6 | 32:9.11.36-16.el8_10.6 | Oct 22, 2025 | Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11 | |
| CVE-2024-11187 | Hig | 7.5 | < 32:9.11.36-16.el8_10.4 | 32:9.11.36-16.el8_10.4 | Jan 29, 2025 | It is possible to construct a zone such that some queries to it will generate responses containing numerous records in the Additional section. An attacker sending many such queries can cause either the authoritative server itself or an independent resolver to use disproportionate | |
| CVE-2024-4076 | Hig | 7.5 | < 32:9.16.23-18.el9_4.6 | 32:9.16.23-18.el9_4.6 | Jul 23, 2024 | Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result in an assertion failure. This issue affects BIND 9 versions 9.16.13 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.33-S1 through 9.11.37 | |
| CVE-2024-1975 | Hig | 7.5 | < 32:9.16.23-18.el9_4.6 | 32:9.16.23-18.el9_4.6 | Jul 23, 2024 | 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 affects BIND 9 versions | |
| CVE-2024-1737 | Hig | 7.5 | < 32:9.16.23-18.el9_4.6 | 32:9.16.23-18.el9_4.6 | Jul 23, 2024 | 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 issue affects BIND 9 ver | |
| CVE-2023-50868 | Hig | 7.5 | < 32:9.11.36-11.el8_9.1 | 32:9.11.36-11.el8_9.1 | Feb 14, 2024 | The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 51 | |
| CVE-2023-50387 | Hig | 7.5 | < 32:9.11.36-11.el8_9.1 | 32:9.11.36-11.el8_9.1 | Feb 14, 2024 | Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with man | |
| CVE-2023-6516 | Hig | 7.5 | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | Feb 13, 2024 | To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first alloc | |
| CVE-2023-5679 | Hig | 7.5 | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | Feb 13, 2024 | A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9 |
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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, and 9.20.9-S1 throug
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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.11.0 through 9.18.50,
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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, which can result in cac
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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 can be orders of magni
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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 also may lead to an
- affected < 32:9.16.23-40.el9_8.8fixed 32:9.16.23-40.el9_8.8
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 9.18.50-S1, and 9.20.
- affected < 32:9.18.33-15.el10_2.2fixed 32:9.18.33-15.el10_2.2
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 crafted requests reaching t
- affected < 32:9.18.33-15.el10_2.2fixed 32:9.18.33-15.el10_2.2
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 integrated DNS deployments
- affected < 32:9.16.23-34.el9_7.2fixed 32:9.16.23-34.el9_7.2
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see:
- affected < 32:9.18.33-10.el10_1.2fixed 32:9.18.33-10.el10_1.2
Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion. This issue affects BIND 9 versions 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 thr
- affected < 32:9.18.33-10.el10_1.2fixed 32:9.18.33-10.el10_1.2
In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9.
- affected < 32:9.11.36-16.el8_10.6fixed 32:9.11.36-16.el8_10.6
Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11
- affected < 32:9.11.36-16.el8_10.4fixed 32:9.11.36-16.el8_10.4
It is possible to construct a zone such that some queries to it will generate responses containing numerous records in the Additional section. An attacker sending many such queries can cause either the authoritative server itself or an independent resolver to use disproportionate
- affected < 32:9.16.23-18.el9_4.6fixed 32:9.16.23-18.el9_4.6
Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result in an assertion failure. This issue affects BIND 9 versions 9.16.13 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.33-S1 through 9.11.37
- affected < 32:9.16.23-18.el9_4.6fixed 32:9.16.23-18.el9_4.6
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 affects BIND 9 versions
- affected < 32:9.16.23-18.el9_4.6fixed 32:9.16.23-18.el9_4.6
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 issue affects BIND 9 ver
- affected < 32:9.11.36-11.el8_9.1fixed 32:9.11.36-11.el8_9.1
The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 51
- affected < 32:9.11.36-11.el8_9.1fixed 32:9.11.36-11.el8_9.1
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with man
- affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first alloc
- affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9
Page 1 of 2