A broken inbound incremental zone update (IXFR) can cause named to terminate unexpectedly
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR triggering the flaw described above, the named process will terminate due to a failed assertion the next time the transferred secondary zone is refreshed.
Timeline
- CVE published
- Record last updated
Affected versions
- ISC BIND9
Open Source Branch 9.8 9.8.5 through 9.8.8, Open Source Branches 9.9 through 9.11 9.9.3 through versions before 9.11.30, Open Source Branches 9.12 through 9.16 9.12.0 through versions before 9.16.14, Supported Preview Branches 9.9-S through 9.11-S 9.9.3-S1 through versions before 9.11.30-S1, Supported Preview Branch 9.16-S 9.16.8-S1 through versions before 9.16.14-S1, Development Branch 9.17 9.17.0 through versiosn before 9.17.12