First published: Mon Feb 12 2024(Updated: )
A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.
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 | |
NetApp Active IQ Unified Manager for VMware vSphere | ||
Fedora | =38 | |
Fedora | =39 | |
ISC BIND 9 | >=9.16.12<=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.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.16.45-s1 | |
ISC BIND 9 | =9.18.11-s1 | |
ISC BIND 9 | =9.18.18-s1 | |
ISC BIND 9 | =9.18.21-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-5679 is considered a medium severity vulnerability due to its potential to cause crashes in affected systems.
To fix CVE-2023-5679, update BIND to versions 9.16.48, 9.18.24, or 9.19.21 to resolve the issue.
CVE-2023-5679 affects BIND versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, and 9.19.0 through 9.19.19.
Symptoms of CVE-2023-5679 include assertion failures and crashes of the 'named' service when recursive resolution is in use.
Disabling either DNS64 or serve-stale features may serve as a temporary workaround for CVE-2023-5679 until a patch is applied.