rpm package
almalinux/bind-pkcs11
pkg:rpm/almalinux/bind-pkcs11
Vulnerabilities (17)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-1519 | Hig | 7.5 | < 32:9.11.36-16.el8_10.7 | 32:9.11.36-16.el8_10.7 | 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-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-1975 | Hig | 7.5 | < 32:9.11.36-16.el8_10.2 | 32:9.11.36-16.el8_10.2 | 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.11.36-16.el8_10.2 | 32:9.11.36-16.el8_10.2 | 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.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 | — | < 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-4408 | — | < 32:9.11.36-11.el8_9.1 | 32:9.11.36-11.el8_9.1 | 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.11.36-8.el8_8.2 | 32:9.11.36-8.el8_8.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.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.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-3094 | — | < 32:9.11.36-11.el8_9 | 32:9.11.36-11.el8_9 | 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-38178 | — | < 32:9.11.36-3.el8_6.1 | 32:9.11.36-3.el8_6.1 | Sep 21, 2022 | By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources. | ||
| CVE-2022-38177 | — | < 32:9.11.36-3.el8_6.1 | 32:9.11.36-3.el8_6.1 | Sep 21, 2022 | By spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources. | ||
| CVE-2022-2795 | — | < 32:9.11.36-8.el8 | 32:9.11.36-8.el8 | 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. | ||
| CVE-2021-25220 | — | < 32:9.11.36-5.el8 | 32:9.11.36-5.el8 | Mar 23, 2022 | BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including Supported Preview Editions - are also believed to be affected but have | ||
| CVE-2021-25219 | — | < 32:9.11.36-3.el8 | 32:9.11.36-3.el8 | Oct 27, 2021 | In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 -> 9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND 9.17 development branch, exploitation of broken authoritative servers using a | ||
| CVE-2021-25214 | — | < 32:9.11.26-6.el8 | 32:9.11.26-6.el8 | Apr 29, 2021 | In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of n |
- affected < 32:9.11.36-16.el8_10.7fixed 32:9.11.36-16.el8_10.7
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.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.11.36-16.el8_10.2fixed 32:9.11.36-16.el8_10.2
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.11.36-16.el8_10.2fixed 32:9.11.36-16.el8_10.2
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.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
- CVE-2023-50387Feb 14, 2024affected < 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
- CVE-2023-4408Feb 13, 2024affected < 32:9.11.36-11.el8_9.1fixed 32:9.11.36-11.el8_9.1
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.11.36-8.el8_8.2fixed 32:9.11.36-8.el8_8.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.11.36-8.el8_8.1fixed 32:9.11.36-8.el8_8.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-3094Jan 25, 2023affected < 32:9.11.36-11.el8_9fixed 32:9.11.36-11.el8_9
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-38178Sep 21, 2022affected < 32:9.11.36-3.el8_6.1fixed 32:9.11.36-3.el8_6.1
By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.
- CVE-2022-38177Sep 21, 2022affected < 32:9.11.36-3.el8_6.1fixed 32:9.11.36-3.el8_6.1
By spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.
- CVE-2022-2795Sep 21, 2022affected < 32:9.11.36-8.el8fixed 32:9.11.36-8.el8
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.
- CVE-2021-25220Mar 23, 2022affected < 32:9.11.36-5.el8fixed 32:9.11.36-5.el8
BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including Supported Preview Editions - are also believed to be affected but have
- CVE-2021-25219Oct 27, 2021affected < 32:9.11.36-3.el8fixed 32:9.11.36-3.el8
In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 -> 9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND 9.17 development branch, exploitation of broken authoritative servers using a
- CVE-2021-25214Apr 29, 2021affected < 32:9.11.26-6.el8fixed 32:9.11.26-6.el8
In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of n