# CVE-2024-0760: A flood of DNS messages over TCP may make the server unstable

> A malicious client can cause instability in the BIND DNS server by flooding it with TCP DNS messages, leading to a denial of service.

- **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-0760, AZL-46972, BELL-CVE-2024-0760, DEBIAN-CVE-2024-0760, GHSA-v3r3-642v-rqj8, OESA-2024-2016, OESA-2024-2017, UBUNTU-CVE-2024-0760

## What is CVE-2024-0760?

CVE-2024-0760 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

A malicious client can send many DNS messages over TCP, potentially causing the server to become unstable while the attack is in progress. The server may recover after the attack ceases. Use of ACLs will not mitigate the attack. 
This issue affects BIND 9 versions 9.18.1 through 9.18.27, 9.19.0 through 9.19.24, and 9.18.11-S1 through 9.18.27-S1.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

Upgrade to a fixed version.

## Is CVE-2024-0760 being exploited?

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

Public exploit code:

- CVE-2024-0760 (github_poc): https://github.com/SpiralBL0CK/CVE-2024-0760

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0760 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-0760 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-0760/ (Markdown: https://insights.sbomify.com/CVE-2024-0760/index.md)
```

## Sources

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

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