This issue affects BIND 9 versions 9.16.33 through 9.16.41, 9.18.7 through 9.18.15, 9.16.33-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1.
Metrics
Affected Vendors & Products
Source | ID | Title |
---|---|---|
![]() |
DSA-5439-1 | bind9 security update |
![]() |
EUVD-2023-34357 | If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and `stale-answer-client-timeout 0;`, a sequence of serve-stale-related lookups could cause `named` to loop and terminate unexpectedly due to a stack overflow. This issue affects BIND 9 versions 9.16.33 through 9.16.41, 9.18.7 through 9.18.15, 9.16.33-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1. |
![]() |
USN-6183-1 | Bind vulnerabilities |
Solution
Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.42, 9.18.16, 9.16.42-S1, or 9.18.16-S1.
Workaround
Setting `stale-answer-client-timeout` to `off` or to a non-zero value prevents the issue. Users of versions 9.18.10, 9.16.36, 9.16.36-S1 or older who are unable to upgrade should set `stale-answer-client-timeout` to `off`; using a non-zero value with these older versions leaves `named` vulnerable to CVE-2022-3924. Although it is possible to set the `recursive-clients` limit to a high number to reduce the likelihood of this scenario, this is not recommended; the limit on `recursive-clients` is important for preventing exhaustion of server resources. The limit cannot be disabled entirely.
Fri, 06 Dec 2024 19:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|

Status: PUBLISHED
Assigner: isc
Published:
Updated: 2025-02-13T16:49:00.351Z
Reserved: 2023-05-26T11:20:45.872Z
Link: CVE-2023-2911

Updated: 2024-08-02T06:41:03.760Z

Status : Modified
Published: 2023-06-21T17:15:47.827
Modified: 2024-11-21T07:59:33.147
Link: CVE-2023-2911


No data.