Outdated ISC BIND
A DNS server runs a version of ISC BIND older than the releases fixing published ISC advisories, most often flaws that let a remote attacker stop the service.
| Severity | Medium |
| CVSS 3.1 | 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Open in the calculator |
| CVSS 4.0 | 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1499.004 Application or System Exploitation |
| Category | Outdated Components |
Description
A DNS server is running a version of ISC BIND 9 older than the releases that fix vulnerabilities published in ISC's security advisories, or a branch that ISC no longer supports. BIND is one of the most widely used DNS servers, acting as an authoritative server, a recursive resolver or both.
Most BIND vulnerabilities let a remote attacker who can send queries to the server, or cause it to receive crafted responses, stop the named process, for example by triggering an assertion failure with a crafted query or response, or exhaust its CPU or memory. CVE-2015-5477, in which a crafted TKEY query crashed the server, is a long-standing example, and the KeyTrap issue CVE-2023-50387 showed how crafted DNSSEC data could tie up validating resolvers. For an authoritative server, an outage makes the organisation's domains fail to resolve for external users, interrupting websites, email and other services; for an internal resolver, it can stop users and systems from reaching anything by name. The effect normally lasts until the service restarts, but repeated attacks can keep it down.
Many flaws affect only resolvers, or only servers with particular features enabled, so the exposure depends on the server's role and configuration: servers that answer queries from the internet, and resolvers that accept recursive queries from untrusted networks, are most exposed. Flaws allowing cache poisoning or code execution are rarer, so confidentiality and integrity are rarely affected, though cache poisoning flaws could let an attacker redirect users to systems they control.
BIND returns its version in response to a CHAOS-class TXT query for version.bind unless its configuration changes this, and scanners compare that string with ISC's advisories. Linux distributions backport fixes into older version numbers, so the distribution's advisories or a credentialed check of the package release give a reliable answer. ISC supports a limited number of stable and Extended Support Version branches at a time, and older branches stop receiving fixes.
Remediation
Upgrade BIND to a supported release that contains all published fixes:
- Apply the distribution's latest BIND security updates through the package manager or, where BIND is built from source, upgrade to the latest release of a branch that ISC still supports. Plan the move off any branch that has reached end of life.
- Subscribe to ISC's security advisories or the distribution's announcements; ISC usually releases each fix for all supported branches at the same time.
- Where the server runs on an appliance, install the vendor's latest firmware, as the BIND version is controlled by the vendor.
Reduce exposure while updates are planned: limit recursion to internal clients with allow-recursion, keep authoritative and recursive roles on separate servers, restrict zone transfers to known secondary servers, and apply any configuration workaround that an advisory gives. Setting the version option to a neutral string hides the version from casual queries, but it fixes nothing and is no substitute for upgrading.
Confirm the fix by checking the installed package release against the distribution's advisories, or the version reported by named -v against the fixed releases in each ISC advisory.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.