Reachable Assertion Affecting bind9 package, versions <1:9.18.11-1
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-DEBIANUNSTABLE-BIND9-3248391
- published 26 Jan 2023
- disclosed 26 Jan 2023
Introduced: 26 Jan 2023
CVE-2022-3924 Open this link in a new tabHow to fix?
Upgrade Debian:unstable bind9 to version 1:9.18.11-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream bind9 package and not the bind9 package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
This issue can affect BIND 9 resolvers with stale-answer-enable yes; that also make use of the option stale-answer-client-timeout, configured with a value greater than zero.
If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM recursive-clients limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure.
This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.