Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2015-5477: ISC BIND TKEY Query Assertion Denial of Service

Published Jul 29, 2015 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS99.6%100th percentile
CISA KEVYesAdded Oct 8, 2026
In the wildActivePer CISA KEV
Vendors
Internet Systems ConsortiumNetAppDebian ProjectHewlett Packard EnterpriseRed HatOpensuseFedora ProjectJuniper Networks
IdentifiersCVE-2015-5477CWE-617 · Reachable Assertion

CVE-2015-5477 is a remotely reachable assertion vulnerability in ISC BIND 9's handling of DNS TKEY queries. A single specially crafted query triggers a REQUIRE assertion failure and terminates the DNS daemon. Affected versions include 9.1.0 through 9.8.x, 9.9.0 through 9.9.7-P1, and 9.10.0 through 9.10.2-P2. Both recursive and authoritative servers are vulnerable. Processing reaches the vulnerable code before BIND access-control lists and service restrictions are evaluated, so those settings do not prevent exploitation. Public exploit code has existed since 2015, and the vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation terminates the BIND DNS service, interrupting recursive resolution or authoritative DNS responses. Resulting DNS outages can disrupt dependent web, email, and other services. Repeated exploitation can cause recurring outages after service restarts. The established impact is loss of availability; this vulnerability does not establish confidentiality loss, data modification, or arbitrary code execution.

Mitigation

If you can’t patch tonight, do this now.

ISC identified no BIND configuration workaround: application-level access-control lists and service restrictions do not block the vulnerable processing path. Pending patching, restrict access to UDP and TCP port 53 using external network controls wherever public access is unnecessary. Network IDS/IPS signatures or filtering unauthorized TKEY queries, DNS record type 249, can provide compensating protection. Isolate or disable the service if necessary and operationally feasible. Automatic service restart can reduce downtime but does not prevent repeated exploitation. Monitor for assertion failures, unexpected DNS daemon exits, and suspicious TKEY traffic.

Remediation

Patch, then assume compromise.

Upgrade to a currently supported BIND release containing the fix, or install the applicable operating-system or appliance vendor's corrected package or firmware. The original fixed releases were BIND 9.9.7-P2 and 9.10.2-P3, but those branches are now unsupported and should not be selected as long-term upgrade targets. Restart the DNS service after updating and verify that the running instance uses the corrected software. Assess embedded BIND installations in DNS appliances, firewalls, and routers as well as standalone servers.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
bind_tkey.rbThis repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/dns/bind_tkey.rb) that exploits CVE-2015-5477, a denial-of-service vulnerability in ISC BIND9 DNS servers. The module constructs and sends a malformed DNS TKEY query packet to the target's UDP port 53. If the target is running a vulnerable version of BIND9, the server will crash with a REQUIRE assertion failure, resulting in a denial of service. The exploit allows optional spoofing of the source address. The code is written in Ruby and leverages Metasploit's auxiliary and UDP scanner modules. No hardcoded IPs or domains are present; the target is specified by the user. The repository is operational and suitable for use in testing or attacking vulnerable BIND9 instances.Disclosed Jul 28, 2015 · Framework: metasploit · ruby · networkWeaponizedcve-2015-5477This repository contains a proof-of-concept (PoC) exploit for CVE-2015-5477, a denial-of-service vulnerability in ISC BIND9's TKEY record processing. The repository consists of a single C source file (tkill.c) and a README.md. The exploit works by sending a specially crafted UDP packet (the 'dospacket') to the target's DNS service (port 53), which triggers an assertion failure and crashes the server. The code supports both IPv4 and IPv6, and can target multiple hosts or IPs specified on the command line. The exploit first sends a version query to check if the server is up, then sends the DoS packet, and waits to see if the server becomes unresponsive. The payload is hardcoded in the source and is not customizable. The exploit is cross-platform and can be compiled and run on Linux, macOS, and Windows (with appropriate toolchains). The README provides usage instructions and background on the vulnerability. The only notable endpoint in the code is a reference URL embedded in the DoS packet, which points to the exploit's GitHub repository.robertdavidgraham · Disclosed Jul 31, 2015 · c · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleOs X Serveroperating_system
CanonicalUbuntu Linuxoperating_system
Debian ProjectDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
Hewlett Packard EnterpriseDnsapplication
Hewlett Packard EnterpriseHp-Uxoperating_system
Hewlett Packard EnterpriseOpenvmsapplication
Hewlett Packard EnterpriseVcxapplication
Internet Systems ConsortiumBindapplication
Juniper NetworksJunosoperating_system
NetAppClustered Data Ontapoperating_system
OpensuseEvergreenoperating_system
OpensuseOpensuseoperating_system
Oracle CorporationSolarisapplication
Oracle CorporationVm Serveroperating_system
Red HatEnterprise Linux Ausoperating_system
Red HatRed Hat Enterprise Linuxoperating_system
SuseLinux Enterprise Debuginfoapplication
SuseLinux Enterprise Software Development Kitoperating_system
SuseSuse Linux Enterprise Desktopoperating_system
SuseSuse Linux Enterprise Serveroperating_system
FAQ

Frequently asked questions

Is CVE-2015-5477 exploited in the wild?
Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 8, 2026.
Is there a public exploit for CVE-2015-5477?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2015-5477, the earliest disclosed Jul 28, 2015.
Is there a patch for CVE-2015-5477?
Upgrade to a currently supported BIND release containing the fix, or install the applicable operating-system or appliance vendor's corrected package or firmware. The original fixed releases were BIND 9.9.7-P2 and 9.10.2-P3, but those branches are now unsupported and should not be selected as long-term upgrade targets.
What products are affected by CVE-2015-5477?
Internet Systems Consortium Bind, Hewlett Packard Enterprise Dns, NetApp Clustered Data Ontap, Debian Project Debian Linux, Red Hat Enterprise Linux Aus, and at least 16 more.
How severe is CVE-2015-5477?
CVE-2015-5477 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 99.6% (100th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence8Every report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity13Community discussion across Reddit, Mastodon, and other social sources.