rpm package
almalinux/bind-doc
pkg:rpm/almalinux/bind-doc
Vulnerabilities (22)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| 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-4.el10_0.2 | 32:9.18.33-4.el10_0.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-4.el10_0.2 | 32:9.18.33-4.el10_0.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.18.33-4.el10_0.2 | 32:9.18.33-4.el10_0.2 | 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.16.23-24.el9_5.3 | 32:9.16.23-24.el9_5.3 | 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 | — | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | 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 | — | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | 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 | — | < 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 | — | < 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 | ||
| CVE-2023-5517 | — | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | Feb 13, 2024 | A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect ;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response | ||
| CVE-2023-4408 | — | < 32:9.16.23-14.el9_3.4 | 32:9.16.23-14.el9_3.4 | Feb 13, 2024 | The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. T | ||
| CVE-2023-3341 | — | < 32:9.16.23-11.el9_2.2 | 32:9.16.23-11.el9_2.2 | Sep 20, 2023 | The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of avai | ||
| CVE-2023-2828 | — | < 32:9.16.23-11.el9_2.1 | 32:9.16.23-11.el9_2.1 | Jun 21, 2023 | Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the con | ||
| CVE-2022-3924 | — | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 25, 2023 | This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase | ||
| CVE-2022-3736 | — | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 25, 2023 | BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to a positive integer, and the resolver receives an RRSIG query. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 throug | ||
| CVE-2022-3094 | — | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 25, 2023 | 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 checking of access p | ||
| CVE-2022-2795 | — | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Sep 21, 2022 | By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the resolver's performance, effectively denying legitimate clients access to the DNS resolution service. |
- 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-4.el10_0.2fixed 32:9.18.33-4.el10_0.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-4.el10_0.2fixed 32:9.18.33-4.el10_0.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.18.33-4.el10_0.2fixed 32:9.18.33-4.el10_0.2
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.16.23-24.el9_5.3fixed 32:9.16.23-24.el9_5.3
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
- CVE-2023-50868Feb 14, 2024affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
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-50387Feb 14, 2024affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
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-6516Feb 13, 2024affected < 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
- CVE-2023-5679Feb 13, 2024affected < 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
- CVE-2023-5517Feb 13, 2024affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect ;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response
- CVE-2023-4408Feb 13, 2024affected < 32:9.16.23-14.el9_3.4fixed 32:9.16.23-14.el9_3.4
The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. T
- CVE-2023-3341Sep 20, 2023affected < 32:9.16.23-11.el9_2.2fixed 32:9.16.23-11.el9_2.2
The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of avai
- CVE-2023-2828Jun 21, 2023affected < 32:9.16.23-11.el9_2.1fixed 32:9.16.23-11.el9_2.1
Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the con
- CVE-2022-3924Jan 25, 2023affected < 32:9.16.23-11.el9fixed 32:9.16.23-11.el9
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase
- CVE-2022-3736Jan 25, 2023affected < 32:9.16.23-11.el9fixed 32:9.16.23-11.el9
BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to a positive integer, and the resolver receives an RRSIG query. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 throug
- CVE-2022-3094Jan 25, 2023affected < 32:9.16.23-11.el9fixed 32:9.16.23-11.el9
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 checking of access p
- CVE-2022-2795Sep 21, 2022affected < 32:9.16.23-11.el9fixed 32:9.16.23-11.el9
By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the resolver's performance, effectively denying legitimate clients access to the DNS resolution service.
Page 1 of 2