CVE-2015-5477

HIGHCVSS v2 · 7.87.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.8 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 91.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 91%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 91%CVSS v2: 7.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

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.

CVSS v2.0 (legacy)
7.8HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.8(low)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation91% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
91%
EPSS %ILE
100%
KEV
Not listed

Published

July 29, 2015

Last Modified

May 6, 2026

References (84)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9 (1:9.8.1.dfsg.P1-4ubuntu0.12) @ precise2026-07-26ubuntu
redhatbind-32:9.8.2-0.30.rc1.el6_6.42016-01-28redhat
redhatbind-32:9.8.2-0.23.rc1.el6_5.22016-01-28redhat
redhatbind-32:9.9.4-18.ael7b_1.32015-07-29redhat
redhatbind-30:9.3.6-25.P1.el5_11.32015-07-28redhat
redhatbind97-32:9.7.0-21.P2.el5_11.22015-07-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.9.5.dfsg-11—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.9.5.dfsg-11—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.9.5.dfsg-11—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.9.5.dfsg-11—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
bind91:9.7.2.dfsg.P3-1.1 ... 1:9.7.3.dfsg-1~squeeze9 (19 versions)1:9.7.3.dfsg-1~squeeze16—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
bind91:9.8.4.dfsg.P1-6+nmu2 ... 1:9.8.4.dfsg.P1-6+nmu2+deb7u5 (8 versions)1:9.8.4.dfsg.P1-6+nmu2+deb7u6—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
bind91:9.9.5.dfsg-9, 1:9.9.5.dfsg-9+deb8u11:9.9.5.dfsg-9+deb8u2—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-16 14:51 UTCEPSS rescore
  2. 2026-08-16 02:09 UTCEPSS rescore
  3. 2026-08-11 01:01 UTCOSV refresh
  4. 2026-08-08 16:32 UTCEPSS rescore
  5. 2026-08-07 16:22 UTCEPSS rescore
  6. 2026-07-30 01:26 UTCEPSS rescore
  7. 2026-07-30 01:26 UTCEPSS rescore
  8. 2026-07-26 13:54 UTCEG score recompute▲ 7.80
  9. 2026-07-26 01:32 UTCVendor advisory
  10. 2026-07-26 01:32 UTCGHSA enrichment
  11. 2026-07-26 01:31 UTCVendor advisory
  12. 2026-07-26 01:31 UTCGHSA enrichment
  13. 2026-07-26 01:30 UTCVendor advisory
  14. 2026-07-26 01:30 UTCGHSA enrichment
  15. 2026-07-26 01:29 UTCVendor advisory
  16. 2026-07-26 01:29 UTCGHSA enrichment
  17. 2026-07-26 01:28 UTCVendor advisory
  18. 2026-07-26 01:28 UTCGHSA enrichment
  19. 2026-07-26 01:27 UTCVendor advisory
  20. 2026-07-26 01:27 UTCGHSA enrichment
  21. 2026-07-26 01:27 UTCVendor advisory
  22. 2026-07-26 01:26 UTCGHSA enrichment
  23. 2026-07-26 01:25 UTCVendor advisory
  24. 2026-07-26 01:25 UTCGHSA enrichment
  25. 2026-07-26 01:24 UTCVendor advisory
Show 75 more
  1. 2026-07-26 01:24 UTCGHSA enrichment
  2. 2026-07-26 01:23 UTCVendor advisory
  3. 2026-07-26 01:23 UTCGHSA enrichment
  4. 2026-07-26 01:22 UTCVendor advisory
  5. 2026-07-26 01:22 UTCGHSA enrichment
  6. 2026-07-26 01:21 UTCVendor advisory
  7. 2026-07-26 01:21 UTCGHSA enrichment
  8. 2026-07-26 01:20 UTCVendor advisory
  9. 2026-07-26 01:20 UTCGHSA enrichment
  10. 2026-07-26 01:19 UTCVendor advisory
  11. 2026-07-26 01:19 UTCGHSA enrichment
  12. 2026-07-26 01:18 UTCVendor advisory
  13. 2026-07-26 01:18 UTCGHSA enrichment
  14. 2026-07-26 01:17 UTCVendor advisory
  15. 2026-07-26 01:17 UTCGHSA enrichment
  16. 2026-07-26 01:16 UTCVendor advisory
  17. 2026-07-26 01:16 UTCGHSA enrichment
  18. 2026-07-26 01:15 UTCVendor advisory
  19. 2026-07-26 01:15 UTCGHSA enrichment
  20. 2026-07-26 01:14 UTCVendor advisory
  21. 2026-07-26 01:14 UTCGHSA enrichment
  22. 2026-07-26 01:13 UTCVendor advisory
  23. 2026-07-26 01:13 UTCGHSA enrichment
  24. 2026-07-26 01:12 UTCVendor advisory
  25. 2026-07-26 01:12 UTCGHSA enrichment
  26. 2026-07-26 01:11 UTCVendor advisory
  27. 2026-07-26 01:11 UTCGHSA enrichment
  28. 2026-07-26 01:10 UTCVendor advisory
  29. 2026-07-26 01:10 UTCGHSA enrichment
  30. 2026-07-26 01:09 UTCVendor advisory
  31. 2026-07-26 01:09 UTCGHSA enrichment
  32. 2026-07-26 01:08 UTCVendor advisory
  33. 2026-07-26 01:08 UTCGHSA enrichment
  34. 2026-07-26 01:07 UTCVendor advisory
  35. 2026-07-26 01:07 UTCGHSA enrichment
  36. 2026-07-26 01:06 UTCVendor advisory
  37. 2026-07-26 01:06 UTCGHSA enrichment
  38. 2026-07-26 01:05 UTCVendor advisory
  39. 2026-07-26 01:05 UTCGHSA enrichment
  40. 2026-07-26 01:04 UTCVendor advisory
  41. 2026-07-26 01:04 UTCGHSA enrichment
  42. 2026-07-26 01:04 UTCVendor advisory
  43. 2026-07-26 01:04 UTCGHSA enrichment
  44. 2026-07-26 01:02 UTCVendor advisory
  45. 2026-07-26 01:02 UTCGHSA enrichment
  46. 2026-07-26 01:01 UTCVendor advisory
  47. 2026-07-26 01:01 UTCGHSA enrichment
  48. 2026-07-26 01:00 UTCVendor advisory
  49. 2026-07-26 01:00 UTCGHSA enrichment
  50. 2026-07-26 00:59 UTCVendor advisory
  51. 2026-07-26 00:59 UTCGHSA enrichment
  52. 2026-07-26 00:58 UTCVendor advisory
  53. 2026-07-26 00:58 UTCGHSA enrichment
  54. 2026-07-26 00:57 UTCVendor advisory
  55. 2026-07-26 00:57 UTCGHSA enrichment
  56. 2026-07-26 00:56 UTCVendor advisory
  57. 2026-07-26 00:56 UTCGHSA enrichment
  58. 2026-07-26 00:55 UTCVendor advisory
  59. 2026-07-26 00:55 UTCGHSA enrichment
  60. 2026-07-26 00:54 UTCVendor advisory
  61. 2026-07-26 00:54 UTCGHSA enrichment
  62. 2026-07-26 00:54 UTCVendor advisory
  63. 2026-07-26 00:53 UTCGHSA enrichment
  64. 2026-07-26 00:52 UTCVendor advisory
  65. 2026-07-26 00:52 UTCGHSA enrichment
  66. 2026-07-26 00:51 UTCVendor advisory
  67. 2026-07-26 00:51 UTCGHSA enrichment
  68. 2026-07-26 00:50 UTCVendor advisory
  69. 2026-07-26 00:50 UTCGHSA enrichment
  70. 2026-07-26 00:50 UTCVendor advisory
  71. 2026-07-26 00:49 UTCGHSA enrichment
  72. 2026-07-26 00:48 UTCVendor advisory
  73. 2026-07-26 00:48 UTCGHSA enrichment
  74. 2026-07-26 00:47 UTCVendor advisory
  75. 2026-07-26 00:47 UTCGHSA enrichment

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-37723
    First seen Aug 5, 2015

    ISC BIND 9 - TKEY Remote Denial of Service (PoC)

    Open source ↗
  • Exploit-DBEDB-37721✓ verified
    First seen Aug 1, 2015

    ISC BIND 9 - TKEY (PoC)

    Open source ↗
  • GitHub PoCelceef/tkeypoc
    First seen Aug 1, 2015

    PoC exploit code for CVE-2015-5477 BIND9 TKEY remote DoS vulnerability

    Open source ↗
  • GitHub PoCrobertdavidgraham/cve-2015-5477
    First seen Jul 31, 2015

    PoC exploit for CVE-2015-5477 BIND9 TKEY assertion failure

    Open source ↗
  • Metasploitauxiliary/dos/dns/bind_tkey✓ verified
    First seen Jul 28, 2015

    BIND TKEY Query Denial of Service

    Open source ↗

Frequently asked(4)

What is CVE-2015-5477?
CVE-2015-5477 is a high vulnerability published on July 29, 2015. 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.
When was CVE-2015-5477 disclosed?
CVE-2015-5477 was first published in the National Vulnerability Database on July 29, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-5477 actively exploited?
CVE-2015-5477 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2015-5477?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-5477, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-5477

Explore →

Is Your Infrastructure Affected by CVE-2015-5477?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs