DE EN IT

~/exploited / cve-2015-5477

CVE-2015-5477: ISC BIND

According to CISA this vulnerability is already used in attacks (added on 8 October 2026).

Key facts

CVECVE-2015-5477
VendorISC — BIND
VulnerabilityISC BIND Data Processing Errors Vulnerability
Added8 October 2026
Deadline (US agencies)11 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score7.5 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack over the network, complexity: low, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 99.58%. Higher than 99.9% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-19
CWE-617
Affected versionsjunos: < 12.1
junos: >= 13.1, < 13.2
junos 12.1
junos 12.1r
junos 12.1x44
junos 12.1x45
junos 12.1x46
junos 12.1x47
and 49 more

Description (NVD)

named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion failure and daemon exit) via TKEY queries.

Patches and vendor advisories

Description (CISA)

ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether ISC BIND is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 8 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).