CVE-2024-1737 is an uncontrolled resource-consumption vulnerability in BIND 9 resolver caches and authoritative zone databases. Processing becomes increasingly inefficient when a single DNS owner name contains a very large number of resource records, irrespective of resource-record type. The degradation occurs while records are added or updated and when BIND handles client queries for that name. Affected versions are BIND 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, and corresponding supported subscription releases.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A BIND 9 performance and denial-of-service issue in which a very large number of resource records at the same name can cause database-processing slowdown.
A performance degradation and potential denial-of-service vulnerability in BIND 9 when a very large number of resource records exist at the same name.
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/performance degradation issue in which a very large number of resource records at the same name can make the database slow.
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.