CVE-2022-3924
HIGHEPSS 97th pctlDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 97% of all known CVEs.
References
Related Vulnerabilities
Other CWE-617 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-8617 | High | 7.5 | 93% | - | Fix |
| CVE-2020-36222 | High | 7.5 | 78% | - | Fix |
| CVE-2006-5779 | High | 7.5 | 76% | - | Fix |
| CVE-2021-27212 | High | 7.5 | 64% | - | Fix |
| CVE-2018-5740 | High | 7.5 | 60% | - | Fix |
| CVE-2023-28425 | Medium | 5.5 | 55% | - | Fix |
Common questions
How do I fix CVE-2022-3924?
Published advisories record a fix for 89 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2022-3924 being actively exploited?
Not that we know of. CVE-2022-3924 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 16.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 97% of all scored CVEs.
How severe is CVE-2022-3924?
CVE-2022-3924 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2022-3924 affect?
Published advisories record a fix for bind (Amazon), bind-chroot (Amazon), bind-debuginfo (Amazon), bind-debugsource (Amazon), and 85 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2022-3924
Markdown
[](https://tridentstack.com/cve/CVE-2022-3924)HTML
<a href="https://tridentstack.com/cve/CVE-2022-3924"><img src="https://tridentstack.com/cve/badge/CVE-2022-3924.svg" alt="CVE-2022-3924"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.