For a secondary zone with transfers restricted by TSIG, named may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, named does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
4.3.5-3ubuntu24.3.5-3ubuntu34.3.5-3ubuntu44.3.5-3ubuntu54.3.5-3ubuntu64.3.5-3ubuntu74.3.5-3ubuntu7.14.3.5-3ubuntu7.24.3.5-3ubuntu7.34.3.5-3ubuntu7.41:9.11.16+dfsg-3~build11:9.11.16+dfsg-3~ubuntu11:9.18.39-0ubuntu0.22.04.71:9.18.39-0ubuntu0.24.04.81:9.20.24-1ubuntu0.41:9.20.18-1ubuntu21:9.20.23-1ubuntu11:9.20.24-1ubuntu21:9.20.24-1ubuntu31:9.9.5.dfsg-3ubuntu0.19+esm151:9.10.3.dfsg.P4-8ubuntu1.19+esm111:9.11.3+dfsg-1ubuntu1.19+esm61:9.18.30-0ubuntu0.20.04.2+esm3Exploitability
AV:NAC:HPR:NUI:NScope
S:UImpact
C:NI:HA:LCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L