Attempting QNAME minimization after forwarding can lead to an assertion failure in resolver.c
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 | BIND9 | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
|
No data.
No data available yet.
Vendor Solution
Upgrade to the patched release most closely related to your current version of BIND: BIND 9.16.6 BIND 9.17.4
Vendor Workaround
No workarounds known.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-29469 | In BIND 9.14.0 -> 9.16.5, 9.17.0 -> 9.17.3, If a server is configured with both QNAME minimization and 'forward first' then an attacker who can send queries to it may be able to trigger the condition that will cause the server to crash. Servers that 'forward only' are not affected. |
Ubuntu USN |
USN-4468-1 | Bind vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.1% (3.065% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.