rpm package
almalinux/bind-pkcs11-utils
pkg:rpm/almalinux/bind-pkcs11-utils
Vulnerabilities (30)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-94300 | Hig | 8.1 | < 32:9.11.36-18.el8_10 | 32:9.11.36-18.el8_10 | Oct 21, 2026 | Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attac | |
| CVE-2026-19630 | Hig | 7.5 | < 32:9.11.36-18.el8_10 | 32:9.11.36-18.el8_10 | Oct 21, 2026 | In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with no limit imposed by BIND. A DNS message with a maliciously large number of such structures will cause BIND to consume disproportionate amounts of CPU time and | |
| CVE-2026-80274 | Hig | 7.5 | < 32:9.11.36-16.el8_10.16 | 32:9.11.36-16.el8_10.16 | Sep 16, 2026 | If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects B | |
| CVE-2026-19666 | Hig | 7.5 | < 32:9.11.36-16.el8_10.16 | 32:9.11.36-16.el8_10.16 | Sep 16, 2026 | On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through | |
| CVE-2026-19667 | Hig | 7.5 | < 32:9.11.36-16.el8_10.16 | 32:9.11.36-16.el8_10.16 | Sep 16, 2026 | If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 versions 9.11.0 through 9 | |
| CVE-2026-19662 | Med | 5.9 | < 32:9.11.36-18.el8_10 | 32:9.11.36-18.el8_10 | Sep 16, 2026 | An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of | |
| CVE-2026-13321 | Hig | 8.6 | < 32:9.11.36-16.el8_10.14 | 32:9.11.36-16.el8_10.14 | 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.11.36-16.el8_10.14 | 32:9.11.36-16.el8_10.14 | 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.11.36-16.el8_10.14 | 32:9.11.36-16.el8_10.14 | 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.11.36-16.el8_10.14 | 32:9.11.36-16.el8_10.14 | 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-10723 | Med | 6.8 | < 32:9.11.36-16.el8_10.14 | 32:9.11.36-16.el8_10.14 | 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.11.36-16.el8_10.8 | 32:9.11.36-16.el8_10.8 | 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.11.36-16.el8_10.8 | 32:9.11.36-16.el8_10.8 | 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.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 | 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 |
- affected < 32:9.11.36-18.el8_10fixed 32:9.11.36-18.el8_10
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attac
- affected < 32:9.11.36-18.el8_10fixed 32:9.11.36-18.el8_10
In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with no limit imposed by BIND. A DNS message with a maliciously large number of such structures will cause BIND to consume disproportionate amounts of CPU time and
- affected < 32:9.11.36-16.el8_10.16fixed 32:9.11.36-16.el8_10.16
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects B
- affected < 32:9.11.36-16.el8_10.16fixed 32:9.11.36-16.el8_10.16
On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through
- affected < 32:9.11.36-16.el8_10.16fixed 32:9.11.36-16.el8_10.16
If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 versions 9.11.0 through 9
- affected < 32:9.11.36-18.el8_10fixed 32:9.11.36-18.el8_10
An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of
- affected < 32:9.11.36-16.el8_10.14fixed 32:9.11.36-16.el8_10.14
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.11.36-16.el8_10.14fixed 32:9.11.36-16.el8_10.14
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.11.36-16.el8_10.14fixed 32:9.11.36-16.el8_10.14
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.11.36-16.el8_10.14fixed 32:9.11.36-16.el8_10.14
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.11.36-16.el8_10.14fixed 32:9.11.36-16.el8_10.14
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.11.36-16.el8_10.8fixed 32:9.11.36-16.el8_10.8
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.11.36-16.el8_10.8fixed 32:9.11.36-16.el8_10.8
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.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
- 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
Page 1 of 2