CVE-2024-1975Network attack vector

Remote CPU exhaustion via SIG(0) request flooding

Published Jul 23, 2024 · Updated Feb 13, 2025

Resource exhaustion in ISC BIND 9 affected releases allows remote attackers to make DNS service unresponsive with SIG(0) requests. ISC identifies repeated SIG(0) request processing as the CPU sink but has not published the affected function or exact missing limit. The server must host a zone with a KEY record or cache one from a DNSSEC-signed domain; sustained unauthenticated traffic can exhaust CPU and hang DNS responses.

CVSS severity7.5
High
EPSS probability2.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource exhaustion in ISC BIND 9 affected releases allows remote attackers to make DNS service unresponsive with SIG(0) requests. ISC identifies repeated SIG(0) request processing as the CPU sink but has not published the affected function or exact missing limit. The server must host a zone with a KEY record or cache one from a DNSSEC-signed domain; sustained unauthenticated traffic can exhaust CPU and hang DNS responses.

The record

CVE
CVE-2024-1975
Published
Jul 23, 2024
Updated
Feb 13, 2025
Vendor
Internet Systems Consortium
Product
BIND 9
Classifications
CWE-770, T1499.003
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 23, 2024CVE publishedPublication date reported by the CVE source.
  2. Feb 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=9.0.0 <=9.11.37
  2. Affected versionversion=9.0 <=9.11.37
  3. Affected versionversion=9.16.0 <=9.16.50
  4. Affected versionversion=9.16.8 <=9.16.49-s1
  5. Affected versionversion=9.16.8-S1 <=9.16.49-S1
  6. Affected versionversion=9.18.0 <=9.18.27
  7. Affected versionversion=9.18.11 <=9.18.27-s1
  8. Affected versionversion=9.18.11-S1 <=9.18.27-S1
  9. Affected versionversion=9.19.0 <=9.19.24
  10. Affected versionversion=9.9.3 <=9.11.37-s1
  11. Affected versionversion=9.9.3-S1 <=9.11.37-S1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Internet Systems Consortium · BIND 9version=9.0.0 <=9.11.37; version=9.0 <=9.11.37; version=9.16.0 <=9.16.50; version=9.16.8 <=9.16.49-s1; version=9.16.8-S1 <=9.16.49-S1; version=9.18.0 <=9.18.27; version=9.18.11 <=9.18.27-s1; version=9.18.11-S1 <=9.18.27-S1; version=9.19.0 <=9.19.24; version=9.9.3 <=9.11.37-s1; version=9.9.3-S1 <=9.11.37-S1

Published CVSS scores

7.5Internet Systems ConsortiumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-770Allocation of Resources Without Limits or Throttling
T1499.003Application Exhaustion Flood

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo