Unauthenticated IXFR deltas are applied to the live zone before TSIG verification
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ISC | BIND | >=9.11.0 <=9.18.50, >=9.11.3-S1 <=9.18.50-S1, >=9.20.0 <=9.20.27, >=9.20.9-S1 <=9.20.27-S1, >=9.21.0 <=9.21.25 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in BIND, strongest first
Embed
A live severity badge for an advisory, README or ticket