Affected: Alpaquita:23: bind, Alpaquita:25: bind, Alpaquita:stream: bind

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.

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.

bind-9.20.29-1.1 on GA media

bind: BIND: Unauthorized zone content updates via unauthenticated IXFR deltas bind9: bind: BIND 9: Denial of Service via crafted DNSSEC responses bind: BIND: Denial of Service via malformed DNS64 responses bind9: bind: BIND 9: Denial of Service via 16-bit length truncation in DNS negative cache handling bind: BIND: Denial of Service via invalid DNSSEC records bind9: bind: BIND 9: DNS wildcard record existence can be masked by an attacker via inapplicable NSEC records bind: BIND 9: Denial of Service via crafted query responses bind: BIND: Denial of Service via TKEY query with specific configuration bind9: bind: BIND 9: DNSSEC bypass via NSEC3 insecure-referral proof bind: BIND: Remote Denial of Service via crafted DNS-over-HTTPS request bind: BIND: DNS cache poisoning via malformed zone insertion bind: BIND: Denial of Service via crafted DNSSEC reply bind: BIND resolver: Denial of Service due to resource exhaustion in SVCB/HTTPS AliasMode processing bind: BIND 9: Remote Denial of Service via cached SVCB/HTTPS AliasMode records

Affected: Ubuntu:Pro:14.04:LTS: bind9, Ubuntu:Pro:16.04:LTS: bind9, Ubuntu:Pro:18.04:LTS: bind9, Ubuntu:18.04:LTS: isc-dhcp, Ubuntu:Pro:20.04:LTS: bind9, Ubuntu:20.04:LTS: bind9-libs, Ubuntu:22.04:LTS: bind9, Ubuntu:22.04:LTS: bind9-libs, Ubuntu:24.04:LTS: bind9, Ubuntu:24.04:LTS: isc-dhcp and 2 more

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.

Ein entfernter Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um Daten zu manipulieren, Sicherheitsmaßnahmen zu umgehen oder Denial-of-Service-Zustände herbeizuführen.