A broken inbound incremental zone update (IXFR) can cause named to terminate unexpectedly
At a glance
Severity
MEDIUM 6.5
EPSS
EPSS 6.28 % · percentile 94 (2026-10-27)
State
PUBLISHED
Published
Updated
Assigner
isc
NVD status
Modified
Description
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.
affected Open Source Branch 9.8 9.8.5 through 9.8.8 ; affected Open Source Branches 9.9 through 9.11 9.9.3 through versions before 9.11.30 ; affected Open Source Branches 9.12 through 9.16 9.12.0 through versions before 9.16.14 ; affected Supported Preview Branches 9.9-S through 9.11-S 9.9.3-S1 through versions before 9.11.30-S1 ; affected Supported Preview Branch 9.16-S 9.16.8-S1 through versions before 9.16.14-S1 ; affected Development Branch 9.17 9.17.0 through versiosn before 9.17.12