Improper Input Validation Affecting bind9.16-dnssec-utils package, versions <32:9.16.23-0.14.el8


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.09% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-BIND916DNSSECUTILS-5555015
  • published26 Jan 2023
  • disclosed25 Jan 2023

Introduced: 25 Jan 2023

CVE-2022-3924  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

Upgrade RHEL:8 bind9.16-dnssec-utils to version 32:9.16.23-0.14.el8 or higher.
This issue was patched in RHSA-2023:2792.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bind9.16-dnssec-utils package and not the bind9.16-dnssec-utils package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1