Loading vulnerability…
CVE-2024-0760 is a denial-of-service vulnerability in BIND 9 affecting 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. A malicious client can send many DNS messages over TCP, causing the named server to become unstable while the attack is ongoing. The issue is triggered through network interaction with the server’s TCP-based DNS service and results in operational instability rather than a permanent failure condition. The server may recover once the attack stops.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Python script (CVE-2024-0760.py) that serves as a proof-of-concept exploit for CVE-2024-0760, a vulnerability in ISC BIND. The script constructs and sends a large number (65536) of DNS queries for the domain 'example.com' over TCP to a user-specified DNS server (typically BIND) on port 53. The DNS queries are crafted to include EDNS0 support, and the script prints the raw DNS response if received. The main entry point is the script itself, which requires the target DNS server's IP address as a command-line argument. The exploit demonstrates the ability to flood a DNS server with crafted queries, potentially triggering the vulnerability. No hardcoded IPs or domains are present except for 'example.com', which is used as the query target. The script is a standalone proof-of-concept and does not include advanced payloads or post-exploitation features.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.