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.
7.3.920.2600Exploitability
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