CVE-2022-3924
- Source
- https://cve.org/CVERecord?id=CVE-2022-3924
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-3924.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-3924
- Downstream
- Related
- Published
- 2023-01-26T21:16:03.273Z
- Modified
- 2026-03-13T05:57:38.799750Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
This issue can affect BIND 9 resolvers with
stale-answer-enable yes;that also make use of the optionstale-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-clientslimit 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. - References
Affected packages
Git / gitlab.isc.org/isc-projects/bind9
Database specific
source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-3924.json"
unresolved_ranges
[
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.12-s1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.13-s1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.14-s1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.21-s1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.32-s1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.16.36-s1"
}
]
}
]