Destroying a TLS session early causes assertion failure
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 [-]
| AND |
|
Configuration 3 [-]
| AND |
|
Configuration 4 [-]
| AND |
|
Configuration 5 [-]
| AND |
|
Configuration 6 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
Upgrade to the patched release most closely related to your current version of BIND: BIND 9.18.3 or BIND 9.19.1.
Vendor Workaround
No workarounds known.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-24523 | On vulnerable configurations, the named daemon may, in some circumstances, terminate with an assertion failure. Vulnerable configurations are those that include a reference to http within the listen-on statements in their named.conf. TLS is used by both DNS over TLS (DoT) and DNS over HTTPS (DoH), but configurations using DoT alone are unaffected. Affects BIND 9.18.0 -> 9.18.2 and version 9.19.0 of the BIND 9.19 development branch. |
Ubuntu USN |
USN-5429-1 | Bind vulnerability |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 6.2% (6.243% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.