CVE-2022-3736: named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries
First published: Tue Jan 24 2023(Updated: )
A flaw was found in Bind, where a resolver crash is possible. When stale cache and stale answers are enabled, the option stale-answer-client-timeout is set to a positive integer, and the resolver receives an RRSIG query.
Credit: security-officer@isc.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/bind | <9.16.37 | 9.16.37 |
| redhat/bind | <9.18.11 | 9.18.11 |
| redhat/bind | <9.19.9 | 9.19.9 |
| redhat/bind9.16 | <32:9.16.23-0.14.el8 | 32:9.16.23-0.14.el8 |
| redhat/bind | <32:9.16.23-11.el9 | 32:9.16.23-11.el9 |
| ISC BIND | >=9.16.12<9.16.37 | |
| ISC BIND | >=9.18.0<9.18.11 | |
| ISC BIND | >=9.19.0<9.19.9 | |
| ISC BIND | =9.16.11-s1 | |
| ISC BIND | =9.16.13-s1 | |
| ISC BIND | =9.16.14-s1 | |
| ISC BIND | =9.16.21-s1 | |
| ISC BIND | =9.16.32-s1 | |
| ISC BIND | =9.16.36-s1 |
Remedy
Setting stale-answer-client-timeout to 0 or to off/disabled will prevent BIND from crashing due to this issue.
Remedy
Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.37, 9.18.11, 9.19.9, or 9.16.37-S1.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://kb.isc.org/docs/cve-2022-3736
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2164507
- https://access.redhat.com/errata/RHSA-2023:2261
- https://access.redhat.com/errata/RHSA-2023:2792
- https://access.redhat.com/security/cve/cve-2022-3736
- https://bugzilla.redhat.com/show_bug.cgi?id=2164038
- https://www.cve.org/CVERecord?id=CVE-2022-3736 https://nvd.nist.gov/vuln/detail/CVE-2022-3736 https://kb.isc.org/docs/cve-2022-3736
Frequently Asked Questions
What is the vulnerability ID for this flaw in Bind?
The vulnerability ID for this flaw in Bind is CVE-2022-3736.
What is the severity level of CVE-2022-3736?
The severity level of CVE-2022-3736 is high with a severity value of 7.
How does CVE-2022-3736 affect Bind?
CVE-2022-3736 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.1...
How can I fix the vulnerability in Bind?
To fix the vulnerability in Bind, update to version 9.16.37, 9.18.11, 9.19.9, 32:9.16.23-0.14.el8, or 32:9.16.23-11.el9.
Where can I find more information about CVE-2022-3736?
You can find more information about CVE-2022-3736 at the following references: https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2164507, https://access.redhat.com/errata/RHSA-2023:2261, https://access.redhat.com/errata/RHSA-2023:2792.
- collector/redhat-cve
- collector/nvd-index
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/author
- agent/references
- agent/severity
- agent/weakness
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-3736
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/title
- agent/last-modified-date
- agent/event
- agent/description
- agent/tags
- agent/trending
- package-manager/redhat
- vendor/isc
- canonical/isc bind
- version/isc bind/9.16.12
- version/isc bind/9.18.0
- version/isc bind/9.19.0
- version/isc bind/9.16.11-s1
- version/isc bind/9.16.13-s1
- version/isc bind/9.16.14-s1
- version/isc bind/9.16.21-s1
- version/isc bind/9.16.32-s1
- version/isc bind/9.16.36-s1