A flaw in the networking code handling DNS-over-TLS queries may cause named to terminate unexpectedly due to an assertion failure. This happens when internal data structures are incorrectly reused under significant DNS-over-TLS query load.
This issue affects BIND 9 versions 9.18.0 through 9.18.18 and 9.18.11-S1 through 9.18.18-S1.
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Bind | Isc | 9.18.0 (including) | 9.18.18 (excluding) |
| Bind | Isc | 9.18.11-s1 (including) | 9.18.11-s1 (including) |
| Bind | Isc | 9.18.18-s1 (including) | 9.18.18-s1 (including) |
| Bind9 | Ubuntu | bionic | * |
| Bind9 | Ubuntu | devel | * |
| Bind9 | Ubuntu | jammy | * |
| Bind9 | Ubuntu | lunar | * |
| Bind9 | Ubuntu | mantic | * |
| Bind9 | Ubuntu | noble | * |
| Bind9 | Ubuntu | oracular | * |
| Bind9 | Ubuntu | trusty | * |
| Bind9 | Ubuntu | upstream | * |
| Bind9 | Ubuntu | xenial | * |
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.