7.5
CWE
617 20
Advisory Published
CVE Published
Updated

CVE-2022-3924: Input Validation

First published: Tue Jan 24 2023(Updated: )

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.

Credit: security-officer@isc.org

Affected SoftwareAffected VersionHow to fix
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.12-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

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.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this flaw in Bind?

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

  • What is the severity level of CVE-2022-3924?

    CVE-2022-3924 has a severity level of 7.5 (High).

  • Which software is affected by CVE-2022-3924?

    CVE-2022-3924 affects 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.

  • How can I fix CVE-2022-3924?

    To fix CVE-2022-3924, update the affected BIND software to version 9.16.37 or later.

  • Where can I find more information about CVE-2022-3924?

    You can find more information about CVE-2022-3924 in the following references: [Bugzilla](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2164508) and [Red Hat Advisory RHSA-2023:2261](https://access.redhat.com/errata/RHSA-2023:2261).

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.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203