# CVE-2024-33655: Denial of service in n/a

> Remote attackers can cause denial of service via DNS query accumulation leading to resource consumption and traffic amplification bursts.

- **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:** 6 Jun 2024
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2024-33655, AZL-42447, AZL-42490, CLSA-2026-1780912053, DEBIAN-CVE-2024-33655, GHSA-2xh4-pf7v-vh6h, MGASA-2024-0203, OESA-2024-2231, OESA-2024-2232, OESA-2024-2233, OESA-2024-2234, UBUNTU-CVE-2024-33655, USN-6791-1, openSUSE-SU-2024:13944-1

## What is CVE-2024-33655?

CVE-2024-33655 is a high-severity denial of service vulnerability in n/a, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DNS protocol in RFC 1035 and updates allows remote attackers to cause a denial of service (resource consumption) by arranging for DNS queries to be accumulated for seconds, such that responses are later sent in a pulsing burst (which can be considered traffic amplification in some cases), aka the "DNSBomb" issue.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `unbound` | openSUSE:Tumbleweed | All versions | 1.20.0-1.1 |

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

Apply the vendor's patch.

## Is CVE-2024-33655 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33655 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33655 is a high-severity denial of service vulnerability in n/a, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33655 exists.

Affected product: n/a. 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-33655/ (Markdown: https://insights.sbomify.com/CVE-2024-33655/index.md)
```

## Sources

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

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