named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 19%. No fixed version is recorded.
Processing of repeated responses to the same query, where both responses contain ECS pseudo-options, but where the first is broken in some way, can cause BIND to exit with an assertion failure. 'Broken' in this context is anything that would cause the resolver to reject the query response, such as a mismatch between query and answer name. This issue affects BIND 9 versions 9.11.4-S1 through 9.11.37-S1 and 9.16.8-S1 through 9.16.36-S1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ISC | BIND | >=9.11.4-S1 <=9.11.37-S1, >=9.16.8-S1 <=9.16.36-S1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in BIND, strongest first
Embed
A live severity badge for an advisory, README or ticket