Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or `HESIOD`, or DNS messages that specify meta-classes (`ANY` or `NONE`) in the question section. Specially crafted requests reaching the affected code paths — recursion, dynamic updates (`UPDATE`), zone change notifications (`NOTIFY`), or processing of `IN`-specific record types in non-`IN` data — can cause assertion failures in `named`. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HIsc Bind
APPIsc9.11.0 – 9.16.509.18.0 – 9.18.49 (bez)9.20.0 – 9.20.23 (bez)9.21.0 – 9.21.22 (bez)
Powiązane podatności
Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives...
BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessi...
A use-after-free vulnerability exists within the DNS-over-HTTPS implementation. This issue affects BIND 9 vers...
A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domai...
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may...