A broken inbound incremental zone update (IXFR) can cause named to terminate unexpectedly
ISC BIND9
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ISC BIND9 |
|
ISC BIND9
| Product | Affected | Fixed in |
|---|---|---|
| ISC BIND9 |
|
| No fix yet |
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.
From the CVE record · isc
Affected versions of ISC BIND9 are vulnerable when named receives a malformed IXFR. The named process terminates due to a failed assertion the next time the transferred secondary zone is refreshed. The input does not specify whether authentication is required.
Operators of ISC BIND9 should check versions 9.8.5–9.8.8, 9.9.3–9.11.29, 9.12.0–9.16.13, Supported Preview Edition 9.9.3-S1–9.11.29-S1 and 9.16.8-S1–9.16.13-S1, and development releases 9.17.0–9.17.11.