CVE-2024-33655: Uncontrolled Resource Consumption
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor DNS traffic for abnormal query accumulation patterns and pulsing bursts indicative of exploitation attempts.
- Implement rate limiting on DNS queries to prevent excessive accumulation and burst responses.
- Deploy DNS server software updates and patches as soon as vendors release fixes addressing this vulnerability.
- Use DNS response rate limiting (RRL) features available in many DNS server implementations to mitigate amplification effects.
- Employ network-level protections such as firewalls and intrusion detection/prevention systems configured to detect and block suspicious DNS traffic patterns.
- Segment DNS infrastructure to isolate critical services and reduce the blast radius of potential DoS attacks.
- Collaborate with upstream ISPs and DNS providers to share threat intelligence and coordinate mitigation efforts.
- Conduct regular DNS infrastructure audits and resilience testing to ensure robustness against resource exhaustion attacks.
- Consider deploying DNS over HTTPS (DoH) or DNS over TLS (DoT) to enhance security and potentially reduce exposure to certain attack vectors.
- Prepare incident response plans specifically addressing DNS service disruptions to enable rapid recovery.
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.
References
- datatracker.ietf.org/doc/html/rfc1035 (opens in a new tab)
- nlnetlabs.nl/projects/unbound/security-advisories/ (opens in a new tab)
- github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md (opens in a new tab)
- isc.org/blogs/2024-dnsbomb/ (opens in a new tab)
- nlnetlabs.nl/downloads/unbound/CVE-2024-33655.txt (opens in a new tab)
- github.com/NLnetLabs/unbound/commit/c3206f4568f60c486be6d165b1f2b5b254fea3de (opens in a new tab)
- alas.aws.amazon.com/ALAS-2024-1934.html (opens in a new tab)
- meterpreter.org/researchers-uncover-dnsbomb-a-new-pdos-attack-exploiting-legitimate-dns-features/ (opens in a new tab)
- sp2024.ieee-security.org/accepted-papers.html (opens in a new tab)
- gitlab.isc.org/isc-projects/bind9/-/issues/4398 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QITY2QBX2OCBTZIXD2A5ES62STFIA4AL/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3TBXPRJ2Q235YUZKYDRWOSYNDFBJQWJ3/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/08/msg00019.html (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QITY2QBX2OCBTZIXD2A5ES62STFIA4AL/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TBXPRJ2Q235YUZKYDRWOSYNDFBJQWJ3/ (opens in a new tab)