dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-1737

HIGH · 7.5 CVSS v3.1 Published 2024-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE) can suffer from degraded performance as content is being added or updated, and also when handling client queries for this name. This issue affects BIND 9 versions 9.11.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.4-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.50-S1, and 9.18.11-S1 through 9.18.27-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 confidence

BIND 9 resolver caches and authoritative zone databases experience performance degradation when holding significant numbers of Resource Records (RRs) for the same hostname, affecting both content additions/updates and client query handling. This is a performance-related denial-of-service condition in the DNS server software.

MitigationUpgrade BIND 9 to a patched version beyond the affected ranges (9.11.38+, 9.16.51+, 9.18.28+, 9.19.25+, or corresponding supported release variants). Monitor for high RR counts on single hostnames as a temporary detection method.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed BIND 9 version
    Run 'named -v' or 'named -version' to obtain the exact BIND version number
    Affected if Version is 9.11.0-9.11.37, 9.16.0-9.16.50, 9.18.0-9.18.27, or 9.19.0-9.19.24 (older than patched releases)
  2. Confirm BIND is running as a caching resolver
    Check named.conf for 'recursion yes;' or inspect running process with 'ps aux | grep named' and review configuration for recursive query handling
    Affected if Server is configured as a recursive resolver accepting client queries
  3. Identify authoritative zones with high RR counts per hostname
    Review zone files or use 'dig' to query specific hostnames that may have dozens or hundreds of A/AAAA records (e.g., 'dig hostname.example.com +short' returns many IPs)
    Affected if Any zone contains hostnames with exceptionally large numbers of resource records (dozens to hundreds of RRs for a single name)
  4. Monitor query patterns triggering degradation
    Review query logs or use 'rndc stats' to identify repeated queries for hostnames that resolve to many IP addresses
    Affected if Server handles frequent queries for hostnames with high RR counts, causing noticeable query delays or increased CPU usage
  5. Check for performance degradation symptoms
    Observe named process CPU usage during zone updates or during high query volume for multi-record hostnames using system tools like 'top' or 'ps'
    Affected if Named process shows high CPU usage or query response times increase significantly when handling zones or queries with many RRs per hostname

You are affected if running a BIND 9 version older than 9.11.38/9.16.51/9.18.28/9.19.25 AND the server functions as a resolver or authoritative server serving zones where single hostnames have large numbers of resource records.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BIND 9 to a patched version beyond the affected ranges (9.11.38+, 9.16.51+, 9.18.28+, 9.19.25+, or corresponding supported release variants). Monitor for high RR counts on single hostnames as a temporary detection method.

Recommended fix High confidence

BIND 9.11.38, 9.16.51, 9.18.28, or 9.19.25 (or later stable releases)

  1. 1. Identify current BIND 9 version by running 'named -v' or 'bind -v'
  2. 2. Stop the BIND/named service (e.g., 'systemctl stop named' or 'service named stop')
  3. 3. Upgrade BIND 9 to a fixed version (9.11.38+, 9.16.51+, 9.18.28+, or 9.19.25+) using your system's package manager or by compiling from source
  4. 4. Verify the new version is installed by running 'named -v'
  5. 5. Start the BIND/named service (e.g., 'systemctl start named' or 'service named start')
  6. 6. Monitor logs and test DNS resolution to confirm normal operation
Caveat Upgrading BIND may introduce configuration or behavior changes; review release notes for your target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1737 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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