CVE-2024-12705
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedClients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBIND 9's DNS-over-HTTPS (DoH) implementation is vulnerable to CPU and memory exhaustion via crafted HTTP/2 traffic. Attackers can flood DoH endpoints with valid or invalid HTTP/2 requests, causing resource depletion and service disruption. This is a denial-of-service vulnerability affecting DoH servers running affected BIND 9 versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BIND 9 versionRun 'named -v' or 'named -V' to display the installed BIND versionAffected if The version is lower than 9.18.33, 9.20.5, 9.21.4, or 9.18.33-S1 (if using a stable branch)
-
Check if DoH is configuredSearch configuration files (named.conf) for 'doh' or 'dns-over-https' statements, or check for listen-on ports 443 or 853 with HTTP/2 enabledAffected if DoH is explicitly configured and enabled in the BIND configuration
-
Verify HTTP/2 protocol usage for DoHInspect the DoH configuration block for HTTP/2 settings; check if 'http-version 2' or similar HTTP/2 directives are presentAffected if HTTP/2 is enabled for DoH connections (this is the default in most configurations)
-
Confirm DoH service is listeningRun 'netstat -tlnp | grep -E "(443|853)"' or 'ss -tlnp' to check if BIND is listening on DoH portsAffected if BIND is actively listening on DoH ports (443/tcp or 853/tcp with HTTP/2)
A system is affected if it runs a vulnerable BIND 9 version (pre-9.18.33/9.20.5/9.21.4/9.18.33-S1) with DoH over HTTP/2 enabled and exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade BIND 9 to a patched version (9.18.33+, 9.20.5+, 9.21.4+, or 9.18.33-S1+). Consider implementing rate limiting on DoH endpoints and monitoring for abnormal traffic patterns as additional hardening measures.
BIND 9.18.33+, 9.20.5+, 9.21.4+, or 9.18.33-S1+ (depending on your current branch)
- 1. Identify the currently installed BIND 9 version using 'named -v' or 'bind -v'
- 2. Determine which release branch you are running (9.18.x, 9.20.x, 9.21.x, or 9.18.x-S1)
- 3. Obtain the latest stable BIND 9 release from your operating system vendor or the ISC downloads page at https://www.isc.org/download/
- 4. Upgrade to BIND 9.18.33 or later for the 9.18.x branch, 9.20.5 or later for the 9.20.x branch, 9.21.4 or later for the 9.21.x branch, or 9.18.33-S1 or later for the 9.18.x-S1 branch
- 5. After upgrading, verify the new version is running with 'named -v'
- 6. Monitor CPU and memory usage of the named process to confirm the DoH resource exhaustion issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12705 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data