Skip to content
vulnerability

CVE-2015-5477

7.5
High
KEV · Exploited in wildEPSS 100%Patch available

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.

exploited
Yes, in CISA KEV since 8 Oct 2026fix by 11 Oct 2026 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 99.6%
Published 29 Jul 2015Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply 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.

triage
surface unknownruntimeWAF can block: noAV · networkCWE-19· Common WeaknessCWE-617· Common Weakness

Can a WAF block it? No. The vulnerability is triggered by TKEY queries, which are part of the DNS protocol, not HTTP. Since the attack uses a non-HTTP network protocol, a web application firewall cannot filter or block these requests.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialitynoneintegritynoneavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
common questions

Is CVE-2015-5477 being exploited?

Yes. CVE-2015-5477 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2015-5477?

CVE-2015-5477 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2015-5477?

Yes. A fix has been recorded for CVE-2015-5477. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2015-5477 affect?

CVE-2015-5477 affects juniper:junos, fedoraproject:fedora, redhat:enterprise_linux, redhat:enterprise_linux_aus, and 17 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
juniper:junosfedoraproject:fedoraredhat:enterprise_linuxredhat:enterprise_linux_ausdebian:debian_linuxoracle:vm_serveroracle:solarishp:hp-uxcanonical:ubuntu_linuxnetapp:clustered_data_ontapapple:os_x_serverhpe:dnshp:openvmshpe:vcxsuse:linux_enterprise_debuginfoopensuse:evergreenopensuse:opensusesuse:linux_enterprise_desktopsuse:linux_enterprise_serversuse:linux_enterprise_software_development_kitisc:bind

public exploits

Public exploit code: 2 on Exploit-DB · 1 Metasploit module · 7 GitHub proofs of concept

Exploit-DB
Metasploit
GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 8 Oct 2026 (SSVC 2.0.3).

timeline

  1. 29 Jul 2015Published
  2. 31 Jul 2015First public exploit or proof of concept · 1 day later
  3. 8 Oct 2026Added to CISA KEV (exploited in the wild) · 4,087 days (about 11 years) later
  4. 8 Oct 2026CISA SSVC assessment: exploitation active · same day later
  5. 9 Oct 2026CVE record last updated · 1 day later
  6. 11 Oct 2026CISA remediation due date (US federal agencies) · 2 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 23 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
43 references in the CVE record: 22 advisories, 2 exploits, 19 links
Show 35 more

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved