Skip to main content

ISC Releases Security Advisories for Multiple Versions of BIND 9

Security Updates for the Berkeley Internet Name Domain system

Threat ID:
CC-4252
Threat Severity:
Information only
Published:
27 January 2023 12:33 PM
Report a cyber attack: call 0300 303 5222 or email [email protected]

Summary

Security Updates for the Berkeley Internet Name Domain system

Threat details

Introduction

The Internet Systems Consortium (ISC) has released security updates that address four High vulnerabilities in multiple versions of ISC Berkeley Internet Name Domain (BIND). An attacker could exploit these vulnerabilities to cause a denial-of-service condition.

Remediation advice

Affected organisations are encouraged to review the ISC security advisories and apply the necessary updates or workarounds.

Remediation steps

Type Step
Patch

CVE-2022-3094: An UPDATE message flood may cause named to exhaust all available memory


https://kb.isc.org/v1/docs/cve-2022-3094
Patch

CVE-2022-3488: BIND Supported Preview Edition named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries


https://kb.isc.org/v1/docs/cve-2022-3488
Patch

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


https://kb.isc.org/v1/docs/cve-2022-3736
Patch

CVE-2022-3924: named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota


https://kb.isc.org/v1/docs/cve-2022-3924

Definitive source of threat updates

CVE Vulnerabilities

Status Published

CVE-2022-3094

Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of internal resources rather than memory constraints. This may reduce performance but should not be a significant problem for most servers. Therefore we don't intend to address this for BIND versions prior to BIND 9.16. This issue affects BIND 9 versions 9.16.0 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.8-S1 through 9.16.36-S1.
Status Published

CVE-2022-3488

Processing of repeated responses to the same query, where both responses contain ECS pseudo-options, but where the first is broken in some way, can cause BIND to exit with an assertion failure. 'Broken' in this context is anything that would cause the resolver to reject the query response, such as a mismatch between query and answer name. This issue affects BIND 9 versions 9.11.4-S1 through 9.11.37-S1 and 9.16.8-S1 through 9.16.36-S1.
Status Published

CVE-2022-3736

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

CVE-2022-3924

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.

Last edited: 27 January 2023 12:33 pm