CVE-2022-3924
No exploitation reported by the sources we read.
- Published2023-01-26
- Fixed in9.19.9 · 9.18.11 · 9.16.37
- WeaknessCWE-617
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2023-01-2621:16CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-3924?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-3924?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.19 | ≥ 9.19.0, < 9.19.9 | 9.19.9 | NVD |
| 9.18 | ≥ 9.18.0, < 9.18.11 | 9.18.11 | NVD |
| 9.16 | ≥ 9.16.12, < 9.16.37 | 9.16.37 | NVD |
| 9.16 | = 9.16.12 | no fix published | NVD |
| 9.16 | = 9.16.13 | no fix published | NVD |
| 9.16 | = 9.16.14 | no fix published | NVD |
| 9.16 | = 9.16.21 | no fix published | NVD |
| 9.16 | = 9.16.32 | no fix published | NVD |
| 9.16 | = 9.16.36 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Isc bind to 9.19.9 · 9.18.11 · 9.16.37
Advisories and patches
- kb.isc.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2023-01-26
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-3924?
Is CVE-2022-3924 actively exploited?
What is the CVSS score for CVE-2022-3924?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.