Out-of-zone database nodes can become authoritative zone cuts
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.
A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database. 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