rpm package
almalinux/bind-utils
pkg:rpm/almalinux/bind-utils
Vulnerabilities (35)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-5517 | Hig | 7.5 | < 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 | Hig | 7.5 | < 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 | Hig | 7.5 | < 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 | Hig | 7.5 | < 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 | Hig | 7.5 | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 26, 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 | Hig | 7.5 | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 26, 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 | Hig | 7.5 | < 32:9.16.23-11.el9 | 32:9.16.23-11.el9 | Jan 26, 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-3080 | Hig | 7.5 | < 32:9.16.23-1.el9_0.1 | 32:9.16.23-1.el9_0.1 | Sep 21, 2022 | By sending specific queries to the resolver, an attacker can cause named to crash. | |
| CVE-2022-38178 | Hig | 7.5 | < 32:9.16.23-1.el9_0.1 | 32:9.16.23-1.el9_0.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 | Hig | 7.5 | < 32:9.16.23-1.el9_0.1 | 32:9.16.23-1.el9_0.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 | Med | 5.3 | < 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. | |
| CVE-2021-25220 | Med | 6.8 | < 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-2022-0396 | Med | 5.3 | < 32:9.16.23-5.el9_1 | 32:9.16.23-5.el9_1 | Mar 23, 2022 | BIND 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0 and versions 9.16.11-S1 -> 9.16.26-S1 of the BIND Supported Preview Edition. Specifically crafted TCP streams can cause connections to BIND to remain in CLOSE_WAIT status for an indefinite period of time, even after the client has termina | |
| CVE-2021-25219 | Med | 5.3 | < 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 | Med | 6.5 | < 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.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
- affected < 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
- affected < 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
- affected < 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
- affected < 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
- affected < 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
- affected < 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
- affected < 32:9.16.23-1.el9_0.1fixed 32:9.16.23-1.el9_0.1
By sending specific queries to the resolver, an attacker can cause named to crash.
- affected < 32:9.16.23-1.el9_0.1fixed 32:9.16.23-1.el9_0.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.
- affected < 32:9.16.23-1.el9_0.1fixed 32:9.16.23-1.el9_0.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.
- affected < 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.
- affected < 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
- affected < 32:9.16.23-5.el9_1fixed 32:9.16.23-5.el9_1
BIND 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0 and versions 9.16.11-S1 -> 9.16.26-S1 of the BIND Supported Preview Edition. Specifically crafted TCP streams can cause connections to BIND to remain in CLOSE_WAIT status for an indefinite period of time, even after the client has termina
- affected < 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
- affected < 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
Page 2 of 2