CVE-2021-25215

7.5 HIGH

📋 TL;DR

This vulnerability in BIND DNS servers allows remote attackers to cause denial of service by sending specially crafted DNS queries that trigger an assertion failure, causing the named process to terminate. All currently maintained BIND 9 branches are affected, making this a widespread issue for organizations running BIND DNS servers.

💻 Affected Systems

Products:
  • BIND 9 DNS Server
Versions: BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, BIND 9.9.3-S1 -> 9.11.29-S1, 9.16.8-S1 -> 9.16.13-S1, BIND 9.17.0 -> 9.17.11
Operating Systems: All operating systems running affected BIND versions
Default Config Vulnerable: ⚠️ Yes
Notes: All configurations of affected versions are vulnerable when processing the specific query types that trigger the assertion failure.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete DNS service outage across all affected servers, potentially disrupting all DNS resolution for dependent systems and services.

🟠

Likely Case

Intermittent DNS service disruptions as attackers target vulnerable servers, causing named process crashes and requiring manual restarts.

🟢

If Mitigated

Minimal impact with proper network segmentation, rate limiting, and monitoring to detect and block malicious queries before they reach vulnerable servers.

🌐 Internet-Facing: HIGH - DNS servers are typically internet-facing and directly accessible to attackers who can send malicious queries without authentication.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this, but requires network access to the DNS server.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending specific DNS queries that trigger the assertion failure. The vulnerability is in query processing logic, making it relatively easy to weaponize.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: BIND 9.11.30, 9.16.14, 9.17.12 and later

Vendor Advisory: https://kb.isc.org/docs/cve-2021-25215

Restart Required: Yes

Instructions:

1. Download patched version from ISC website. 2. Stop named service. 3. Install updated BIND package. 4. Start named service. 5. Verify service is running and responding to queries.

🔧 Temporary Workarounds

Query Filtering via Response Policy Zones

all

Use RPZ to block queries for record types known to trigger the vulnerability

# Configure RPZ in named.conf to block problematic queries

Rate Limiting

all

Implement query rate limiting to reduce impact of DoS attempts

# Add rate-limit configuration in named.conf options section

🧯 If You Can't Patch

  • Implement network-level filtering to block malicious DNS queries before they reach BIND servers
  • Deploy redundant DNS servers with load balancing to maintain service during attacks

🔍 How to Verify

Check if Vulnerable:

Check BIND version with 'named -v' or 'rpm -q bind' and compare against affected version ranges

Check Version:

named -v

Verify Fix Applied:

Verify installed version is 9.11.30+, 9.16.14+, or 9.17.12+ and test with known malicious queries

📡 Detection & Monitoring

Log Indicators:

  • named process crashes
  • assertion failure messages in system logs
  • unexpected named service restarts

Network Indicators:

  • Unusual DNS query patterns
  • Specific query types known to trigger the vulnerability
  • Increased DNS query volume

SIEM Query:

source="bind" AND ("assertion failure" OR "named crashed" OR "process terminated")

🔗 References

📤 Share & Export