Loading vulnerability…
CVE-2016-2776 is a reachable assertion failure in the response-construction path of ISC BIND named, specifically while rendering DNS messages into packets in buffer.c. A crafted DNS query meeting particular criteria can cause named to hit an assertion and terminate while constructing its response. Affected versions are BIND releases before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3.
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 (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/dns/bind_tsig.rb) that exploits CVE-2016-2776, a denial-of-service vulnerability in ISC BIND. The module constructs and sends a specially crafted DNS query with a malformed TSIG record to the target's UDP port 53. If the target is running a vulnerable version of BIND, the malformed packet triggers an assertion failure in buffer.c, causing the DNS server to crash. The module allows optional spoofing of the source address and randomizes certain fields in the DNS packet to evade simple detection. The exploit is a proof-of-concept (POC) and does not provide post-exploitation capabilities; its sole purpose is to crash the target service. The code is written in Ruby and is designed to be run within the Metasploit framework.
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.
2 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.