This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.
Metrics
Affected Vendors & Products
Source | ID | Title |
---|---|---|
![]() |
DLA-3726-1 | bind9 security update |
![]() |
DSA-5504-1 | bind9 security update |
![]() |
EUVD-2023-44009 | 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 available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1. |
![]() |
USN-6390-1 | Bind vulnerabilities |
![]() |
USN-6421-1 | Bind vulnerability |
Solution
Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.44, 9.18.19, 9.19.17, 9.16.44-S1, or 9.18.19-S1.
Workaround
By default, `named` only allows control-channel connections over the loopback interface, making this attack impossible to carry out over the network. When enabling remote access to the control channel's configured TCP port, care should be taken to limit such access to trusted IP ranges on the network level, effectively preventing unauthorized parties from carrying out the attack described in this advisory.
Thu, 13 Feb 2025 00:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Redhat rhel Els
|
|
CPEs | cpe:/o:redhat:rhel_els:6 | |
Vendors & Products |
Redhat rhel Els
|

Status: PUBLISHED
Assigner: isc
Published:
Updated: 2025-02-13T16:55:07.169Z
Reserved: 2023-06-20T16:19:13.104Z
Link: CVE-2023-3341

No data.

Status : Modified
Published: 2023-09-20T13:15:11.770
Modified: 2024-11-21T08:17:03.370
Link: CVE-2023-3341


No data.