A too-strict assertion check could be triggered when responses in BIND 9.16.19 and 9.17.16 require UDP fragmentation if RRL is in use
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 [-]
|
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.20 BIND 9.17.17 BIND Supported Preview Edition is a special feature preview branch of BIND provided to eligible ISC support customers. BIND 9.16.20-S1
Vendor Workaround
Disabling RRL in all views, including the built-in CHAOS class view "_bind", prevents the faulty assertion from being reached. This can be done by removing all existing rate-limit statements from named.conf, and defining a replacement for the default CHAOS view: view override_bind chaos { recursion no; notify no; allow-new-zones no; max-cache-size 2M; zone "version.bind" chaos { type primary; database "_builtin version"; }; zone "hostname.bind" chaos { type primary; database "_builtin hostname"; }; zone "authors.bind" chaos { type primary; database "_builtin authors"; }; zone "id.server" chaos { type primary; database "_builtin id"; }; };
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-12129 | In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND 9 releases 9.16.19, 9.17.16, and release 9.16.19-S1 of the BIND Supported Preview Edition. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.7% (3.658% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.