{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3924 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-3924 is a high-severity vulnerability in Isc Bind, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3924 and fix it if it is affected.\n\nWhat it is: CVE-2022-3924 is a high-severity vulnerability in Isc Bind, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-3924 in the wild and no public exploit code.\n\nAffected product: Isc Bind. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-3924/ (Markdown: https://insights.sbomify.com/CVE-2022-3924/index.md)","id":"CVE-2022-3924","markdown":"https://insights.sbomify.com/CVE-2022-3924/index.md","name":"CVE-2022-3924","record":{"aliases":["ALPINE-CVE-2022-3924","AZL-13227","DEBIAN-CVE-2022-3924","GHSA-29px-hvx8-j7xf","UBUNTU-CVE-2022-3924"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"BIND 9 DNS resolver","requires_auth":"none","summary":"A race condition in BIND 9 resolvers with stale answers enabled can cause an assertion failure and unexpected termination under high recursive load.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[{"product":"bind","vendor":"isc"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"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.\n\nIf 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.\nThis 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota","id":"CVE-2022-3924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"isc:bind","products":["isc:bind"],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Buddybadges \u003c= 1.0.0 - Admin+ SQLi","id":"CVE-2022-3925"},"packages":[],"prev":{"headline":"ActiveCampaign for WooCommerce \u003c 1.9.8 - Subscriber+ Error Log Cleanup","id":"CVE-2022-3923"},"products":["BIND 9"],"published":"2023-01-25","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0122","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0010","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0011","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0013","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2000-1029","kev_date_added":null,"published":"2000-11-29"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-1999-0837","kev_date_added":null,"published":"2000-01-04"},{"cvss_score":8.5,"headline":"Denial of service in n/a","id":"CVE-2012-1667","kev_date_added":null,"published":"2012-06-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-31","vendors":["ISC"]},"summary":"A race condition in BIND 9 resolvers with stale answers enabled can cause an assertion failure and unexpected termination under high recursive load.","url":"https://insights.sbomify.com/CVE-2022-3924/"}