Back

MEDIUM

DoS from specifically crafted TCP packets

Published Mar 23, 2022

Description

BIND 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0 and versions 9.16.11-S1 -> 9.16.26-S1 of the BIND Supported Preview Edition. Specifically crafted TCP streams can cause connections to BIND to remain in CLOSE_WAIT status for an indefinite period of time, even after the client has terminated the connection.

Affected products

Remediation

Vendor solution

Upgrade to the patched release most closely related to your current version of BIND: 9.16.27 9.18.1 BIND Supported Preview Edition is a special feature-preview branch of BIND provided to eligible ISC support customers. 9.16.27-S1

Red Hat statement

This issue can only be triggered on BIND servers that have the keep-response-order enabled, which is not the default configuration. The keep-response-order option is an ACL block; any hosts which are specified within it will be able to trigger this issue on affected versions. Only the BIND9.16 package in RHEL-8 and the BIND package in RHEL-9 are affected, because of the presence of vulnerable code in our codebase.

Red Hat mitigation

To mitigate this issue in all affected versions of BIND, use the default setting of : ~~~ keep-response-order { none; } ~~~

Metrics

References (10)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner isc
Published Mar 23, 2022
Updated Sep 16, 2024
Reserved Jan 27, 2022
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Mar 16, 2022