rpm package
almalinux/bind9.18-chroot
pkg:rpm/almalinux/bind9.18-chroot
Vulnerabilities (6)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-1519 | Hig | 7.5 | < 32:9.18.29-5.el9_7.4 | 32:9.18.29-5.el9_7.4 | 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.29-4.el9_6.2 | 32:9.18.29-4.el9_6.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.29-4.el9_6.2 | 32:9.18.29-4.el9_6.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.29-4.el9_6.2 | 32:9.18.29-4.el9_6.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-12705 | Hig | 7.5 | < 32:9.18.29-1.el9_5.1 | 32:9.18.29-1.el9_5.1 | Jan 29, 2025 | Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S | |
| CVE-2024-11187 | Hig | 7.5 | < 32:9.18.29-1.el9_5.1 | 32:9.18.29-1.el9_5.1 | 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 |
- affected < 32:9.18.29-5.el9_7.4fixed 32:9.18.29-5.el9_7.4
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.29-4.el9_6.2fixed 32:9.18.29-4.el9_6.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.29-4.el9_6.2fixed 32:9.18.29-4.el9_6.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.29-4.el9_6.2fixed 32:9.18.29-4.el9_6.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.18.29-1.el9_5.1fixed 32:9.18.29-1.el9_5.1
Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S
- affected < 32:9.18.29-1.el9_5.1fixed 32:9.18.29-1.el9_5.1
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