dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-0760

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
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.

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

This is a denial-of-service vulnerability in BIND 9 where a malicious client can send many DNS messages over TCP, causing the DNS server to become unstable and unavailable. The attack consumes server resources through TCP connections, and ACLs do not mitigate the issue since the traffic appears legitimate. The server may recover after the attack stops.

MitigationUpgrade BIND 9 to a version beyond 9.18.27, 9.19.24, or 9.18.27-S1 (the patched versions). No effective workarounds exist since ACLs do not mitigate this vulnerability.

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 BIND 9 installation and version
    Run 'named -v' or 'named -V' to display the BIND version, or use package management commands such as 'rpm -q bind' or 'dpkg -l bind'
    Affected if The version displayed is earlier than 9.18.27, 9.19.24, or 9.18.27-S1
  2. Confirm TCP is enabled in named.conf
    Inspect the BIND configuration file (typically /etc/named.conf or /etc/bind/named.conf) and look for 'tcp-clients' or 'listen-on' directives that permit TCP connections
    Affected if TCP is explicitly enabled or no restriction is in place to block incoming TCP DNS queries
  3. Verify TCP listener is active
    Run 'netstat -tlnp | grep :53' or 'ss -tlnp | grep :53' to confirm named is listening on TCP port 53
    Affected if The DNS server is accepting TCP connections on port 53
  4. Check for resource consumption indicators
    Monitor for abnormal numbers of established TCP connections to port 53 using 'netstat -an | grep :53 | grep ESTABLISHED' or equivalent
    Affected if An unusually high number of TCP connections are active or in TIME_WAIT state, suggesting resource exhaustion

You are affected if your BIND 9 version is before 9.18.27, 9.19.24, or 9.18.27-S1 AND the server is configured to accept TCP connections on port 53.

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 version beyond 9.18.27, 9.19.24, or 9.18.27-S1 (the patched versions). No effective workarounds exist since ACLs do not mitigate this vulnerability.

Recommended fix High confidence

BIND 9.18.28 (stable) or 9.19.25 (development)

  1. 1. Identify the current BIND 9 version installed using `named -v` or `bind -v`
  2. 2. If running BIND 9.18.x (stable branch), upgrade to version 9.18.28 or later
  3. 3. If running BIND 9.19.x (development branch), upgrade to version 9.19.25 or later
  4. 4. If running a supported preview channel version (9.18.11-S1 through 9.18.27-S1), upgrade to version 9.18.28-S1 or later
  5. 5. After upgrading, verify the server starts successfully and monitor for正常运行
  6. 6. Review ISC KB documentation at kb.isc.org for any additional post-upgrade configuration recommendations
Caveat Upgrading within the same major.minor branch (9.18.x to 9.18.28+) should be low-risk; however, always review release notes for any configuration changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0760 — 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-0760 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