How severe is CVE-2015-5477?

No CVSS score has been assigned to CVE-2015-5477 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-5477?

Affected package information for CVE-2015-5477 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2015-5477?

No fixed release is recorded for CVE-2015-5477 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2015-5477 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2015-5477 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2015-5477 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2015-5477, including 2 documented proof-of-concept exploits on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-5477?

CVE-2015-5477 has an EPSS (Exploit Prediction Scoring System) score of 99.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2015-5477 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2015-5477 ( ISC BIND Data Processing Errors Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-10-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-10-11. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2015-5477?

CVE-2015-5477 is classified as CWE-19 (CWE-19), Reachable Assertion (CWE-617). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2015-5477?

A Metasploit module references CVE-2015-5477, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2015-5477 published, and has it been updated?

CVE-2015-5477 was published on July 29, 2015 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2015-5477 — Red Hat

CVE-2015-5477 is a CWE-19 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-10-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jul 29, 2015

Updated

Apr 16, 2026

Affected

21 products

Patched

See advisory

Exploits

7 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-10-08. Federal agencies were required to remediate by 2026-10-11.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2015-5477.

EPSS Exploitation Probability

via FIRST.org ↗

99.4%probability of exploitation in next 30 days

Very High Risk+8.13%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

21 products · 154 configurations

os x serverapple

1 version

4.1.5

ubuntu linuxcanonical

1 version

12.04

debian linuxdebian

2 versions

7.08.0

fedorafedoraproject

2 versions

2122

hp-uxhp

3 versions

11.1111.2311.31

openvmshp

1 version

5.7

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-37721dosmultiple✓ Verified

ISC BIND 9 - TKEY (PoC)

by Errata Security · Aug 1, 2015

Exploit-DB Source

EDB-37723dosmultiple

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

by elceef · Aug 5, 2015

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2015-5477 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Enterprise Linux 5	`bind-30:9.3.6-25.P1.el5_11.3`	RHSA-2015:1514
Red Hat Enterprise Linux 5	`bind97-32:9.7.0-21.P2.el5_11.2`	RHSA-2015:1515
Red Hat Enterprise Linux 6	`bind-32:9.8.2-0.37.rc1.el6_7.2`	RHSA-2015:1513
Red Hat Enterprise Linux 6.4 Advanced Update Support	`bind-32:9.8.2-0.17.rc1.el6_4.7`	RHSA-2016:0078
Red Hat Enterprise Linux 6.6 Extended Update Support	`bind-32:9.8.2-0.30.rc1.el6_6.4`	RHSA-2016:0079

UbuntuHIGH

USN-2693-1Ubuntu

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2015-5477 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2015-5477 — Red Hat

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2015-5477 in your dependencies?