Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the "recursive-clients" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HIsc Bind
APPIsc9.20.0 – 9.20.23 (bez)9.21.0 – 9.21.22 (bez)
Powiązane podatności
Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Inte...
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...