Loading vulnerability…
CVE-2024-1975 is an uncontrolled resource-consumption vulnerability in BIND 9 SIG(0) request processing. A remote client can send a stream of SIG(0)-signed DNS requests that causes excessive resolver CPU consumption when the server hosts a zone containing a KEY resource record, or when its resolver DNSSEC-validates a KEY resource record obtained from a DNSSEC-signed domain and retained in cache. Affected versions are BIND 9.0.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.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.49-S1, and 9.18.11-S1 through 9.18.27-S1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CPU-exhaustion denial-of-service vulnerability in BIND 9 involving SIG(0) processing.
A BIND 9 denial-of-service vulnerability in which SIG(0) processing can be abused to exhaust CPU resources.
A vulnerability addressed by this Red Hat OpenShift Data Foundation 4.16.2 update; no technical details are provided.
A BIND 9 denial-of-service vulnerability in which SIG(0) requests can exhaust CPU resources.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.