CVE-2020-8625

8.1 HIGH

📋 TL;DR

CVE-2020-8625 is a buffer overflow vulnerability in BIND DNS servers that affects systems configured with GSS-TSIG features. Exploitation could lead to denial of service (named process crash) or potentially remote code execution. This primarily impacts organizations using BIND with Samba integration or in mixed environments with Active Directory domain controllers.

💻 Affected Systems

Products:
  • ISC BIND
Versions: BIND 9.5.0 to 9.11.27, 9.12.0 to 9.16.11, BIND Supported Preview Edition 9.11.3-S1 to 9.11.27-S1 and 9.16.8-S1 to 9.16.11-S1, BIND 9.17 development branch 9.17.0 to 9.17.1
Operating Systems: All operating systems running affected BIND versions
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when tkey-gssapi-keytab or tkey-gssapi-credential options are explicitly configured with valid values

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise

🟠

Likely Case

Denial of service through named process crash

🟢

If Mitigated

No impact if GSS-TSIG is not configured

🌐 Internet-Facing: MEDIUM - Only affects specific GSS-TSIG configurations, not default setups
🏢 Internal Only: HIGH - Internal DNS servers in AD/Samba environments are most vulnerable

🎯 Exploit Status

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

Exploitation requires specific GSS-TSIG configuration and knowledge of the environment

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: BIND 9.11.28, 9.16.12, 9.17.2, and corresponding Supported Preview Edition versions

Vendor Advisory: https://kb.isc.org/v1/docs/cve-2020-8625

Restart Required: Yes

Instructions:

1. Check current BIND version. 2. Download and install patched version from ISC or your distribution's repository. 3. Restart named service. 4. Verify version is updated.

🔧 Temporary Workarounds

Disable GSS-TSIG configuration

all

Remove or comment out tkey-gssapi-keytab and tkey-gssapi-credential options from named.conf

# Edit named.conf and remove lines containing tkey-gssapi-keytab or tkey-gssapi-credential
# Then restart BIND: systemctl restart named

🧯 If You Can't Patch

  • Disable GSS-TSIG features by removing tkey-gssapi configuration options
  • Implement network segmentation to restrict access to BIND servers

🔍 How to Verify

Check if Vulnerable:

Check if BIND version is in affected range AND tkey-gssapi-keytab or tkey-gssapi-credential options are configured in named.conf

Check Version:

named -v

Verify Fix Applied:

Verify BIND version is 9.11.28+, 9.16.12+, or 9.17.2+ using named -v

📡 Detection & Monitoring

Log Indicators:

  • Unexpected named process crashes
  • Segmentation fault errors in system logs
  • GSS-TSIG authentication failures

Network Indicators:

  • Unusual DNS queries to GSS-TSIG enabled zones
  • Traffic spikes to port 53 followed by service disruption

SIEM Query:

source="bind" AND ("segmentation fault" OR "named crashed" OR "SIGSEGV")

🔗 References

📤 Share & Export