# CVE-2023-5679: Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution

> Attackers can crash the BIND DNS server by triggering an assertion failure during recursive resolution when DNS64 and serve-stale are enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2024
- **Updated:** 28 Mar 2025
- **Also known as:** ALPINE-CVE-2023-5679, AZL-34351, AZL-34564, BELL-CVE-2023-5679, DEBIAN-CVE-2023-5679, GHSA-v5qp-mx94-j49v, UBUNTU-CVE-2023-5679

## What is CVE-2023-5679?

CVE-2023-5679 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 13 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2023-5679?

It affects 3 products.


Products: Fedoraproject Fedora, Isc Bind, Netapp Active Iq Unified Manager.

## How do I fix CVE-2023-5679?

Upgrade to a fixed version.

## Is CVE-2023-5679 being exploited?

There is no known exploitation of CVE-2023-5679 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5679 and fix it if it is affected.

What it is: CVE-2023-5679 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 13 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5679 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5679/ (Markdown: https://insights.sbomify.com/CVE-2023-5679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5679
- OSV: https://osv.dev/vulnerability/CVE-2023-5679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5679/
Summaries are generated and may contain mistakes; the official description above is the record.