ISC BIND: attackers can knock it offline
OFFICIAL NAME: ISC BIND Data Processing Errors Vulnerability
WHAT IT IS · SERVERS AND BACKUPSIt runs or protects many systems at once, including your backups.
DO THIS FIRSTPatch it and keep its admin access off the internet. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.
WHY THIS VERDICT Attacks are confirmed. The exploit prediction score is 100%.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- PROOF OF CONCEPT
How far has it climbed?
01 TALK
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCECVE-2015-5477 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries. CISA Vulnrichment marks CVE-2015-5477 as actively exploited.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLIC
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Oct 11, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run ISC BIND? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- Attack activity. JUL 29, 2015CISA Vulnrichment marks CVE-2015-5477 as actively exploited
- JUL 31, 20157 public GitHub repositories claim a proof of concept for CVE-2015-5477
- JUL 31, 2015Exploit-DB entry: ISC BIND 9 - TKEY (PoC)
- AUG 4, 2015Exploit-DB entry: ISC BIND 9 - TKEY Remote Denial of Service (PoC)
- Attack activity. OCT 7, 2026ISC BIND Data Processing Errors Vulnerability
- NOV 6, 2026CVE-2015-5477 discussed publicly (CIRCL sighting)
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: CVE-2015-5477 discussed publicly (CIRCL sighting), NOV 6
- [2] CISA Known Exploited Vulnerabilities: ISC BIND Data Processing Errors Vulnerability, OCT 7
- [3] Exploit-DB: Exploit-DB entry: ISC BIND 9 - TKEY Remote Denial of Service (PoC), AUG 4
- [4] Exploit-DB: Exploit-DB entry: ISC BIND 9 - TKEY (PoC), JUL 31
- [5] PoC-in-GitHub: 7 public GitHub repositories claim a proof of concept for CVE-2015-5477, JUL 31
- [6] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2015-5477 as actively exploited, JUL 29