# CVE-2024-4076: Assertion failure when serving both stale cache data and authoritative zone content

> An attacker can cause a denial of service in BIND by triggering an assertion failure when serving stale cache data alongside authoritative zone content.

- **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:** 23 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** ALPINE-CVE-2024-4076, AZL-46966, AZL-46984, BELL-CVE-2024-4076, DEBIAN-CVE-2024-4076, GHSA-gfw8-mh94-9w58, UBUNTU-CVE-2024-4076

## What is CVE-2024-4076?

CVE-2024-4076 is a high-severity denial of service vulnerability in ISC BIND 9, published on 23 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result in an assertion failure.
This issue affects BIND 9 versions 9.16.13 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.33-S1 through 9.11.37-S1, 9.16.13-S1 through 9.16.50-S1, and 9.18.11-S1 through 9.18.27-S1.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2024-4076?


## How do I fix CVE-2024-4076?

Upgrade to a fixed version.

## Is CVE-2024-4076 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4076 and fix it if it is affected.

What it is: CVE-2024-4076 is a high-severity denial of service vulnerability in ISC BIND 9, published on 23 Jul 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-2024-4076 in the wild and no public exploit code.

Affected product: ISC BIND 9. 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-2024-4076/ (Markdown: https://insights.sbomify.com/CVE-2024-4076/index.md)
```

## Sources

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

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