CVE-2022-3736: named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries

Published 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.

Other sources

BIND 9 resolver can crash when stale cache and stale answers are enabled, option stale-answer-client-timeout is set to a positive integer, and the resolver receives an RRSIG query. 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.

MITRE

BIND 9 resolver can crash when stale cache and stale answers are enabled, option stale-answer-client-timeout is set to a positive integer, and the resolver receives an RRSIG query.

Red Hat

Affected Software

14 affected componentsFixes available
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
redhat/bind<9.16.37
9.16.37
redhat/bind<9.18.11
9.18.11
redhat/bind<9.19.9
9.19.9
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

Remediation

Information

Setting stale-answer-client-timeout to 0 or to off/disabled will prevent BIND from crashing due to this issue.

Information

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.

Event History

Jan 25, 2023
CVE Published
12:00 AM
CVE Published
via MITRE·09:39 PM
Data Sourced
via MITRE·09:39 PM
RemedyDescriptionSeverity
Jan 26, 2023
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID for this flaw in Bind?

The vulnerability ID for this flaw in Bind is CVE-2022-3736.

2

What is the severity level of CVE-2022-3736?

The severity level of CVE-2022-3736 is high with a severity value of 7.

3

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...

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203