First published: Mon Feb 12 2024(Updated: )
Last updated 24 July 2024
Credit: security-officer@isc.org security-officer@isc.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/bind | <9.16.48 | 9.16.48 |
redhat/bind | <9.18.24 | 9.18.24 |
redhat/bind | <9.19.21 | 9.19.21 |
debian/bind9 | 1:9.16.50-1~deb11u2 1:9.16.50-1~deb11u3 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 1:9.20.4-4 1:9.20.5-1 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=17.1.0<=17.1.1 | 17.1.2 |
F5 BIG-IP and BIG-IQ Centralized Management | >=16.1.0<=16.1.4 | 16.1.5 |
F5 BIG-IP and BIG-IQ Centralized Management | >=15.1.0<=15.1.10 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=8.1.0<=8.3.0 | |
NetApp ONTAP | =9.14.1 | |
NetApp ONTAP | =9.15.1 | |
Fedora | =38 | |
Fedora | =39 | |
ISC BIND 9 | >=9.0.0<=9.16.45 | |
ISC BIND 9 | >=9.18.0<=9.18.21 | |
ISC BIND 9 | >=9.19.0<=9.19.19 | |
ISC BIND 9 | =9.9.3-s1 | |
ISC BIND 9 | =9.16.8-s1 | |
ISC BIND 9 | =9.16.11-s1 | |
ISC BIND 9 | =9.16.12-s1 | |
ISC BIND 9 | =9.16.13-s1 | |
ISC BIND 9 | =9.16.14-s1 | |
ISC BIND 9 | =9.16.21-s1 | |
ISC BIND 9 | =9.16.32-s1 | |
ISC BIND 9 | =9.16.36-s1 | |
ISC BIND 9 | =9.16.43-s1 | |
ISC BIND 9 | =9.18.0-s1 | |
ISC BIND 9 | =9.18.11-s1 | |
ISC BIND 9 | =9.18.18-s1 |
Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.48, 9.18.24, 9.19.21, 9.16.48-S1, or 9.18.24-S1.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-4408 has a moderate severity rating due to its potential to cause excessive CPU load under crafted DNS queries.
You can mitigate CVE-2023-4408 by upgrading to the recommended versions of BIND, specifically 9.16.50 or higher, 9.18.28 or higher, or 9.19.21.
CVE-2023-4408 affects various versions of BIND, F5 BIG-IP, F5 BIG-IQ Centralized Management, and specific versions of NetApp ONTAP.
If exploited, CVE-2023-4408 can lead to performance degradation due to increased CPU usage on affected DNS servers.
CVE-2023-4408 is particularly critical in environments with high DNS query volumes or custom query configurations.