named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ISC | BIND 9 | unaffected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Solution
Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.37-S1.
Vendor Workaround
No workarounds known.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-42860 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 19.0% (19.045% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|