CWE
404 459
Advisory Published
Updated

CVE-2022-0396

First published: Wed Mar 16 2022(Updated: )

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.

Credit: security-officer@isc.org security-officer@isc.org

Affected SoftwareAffected VersionHow to fix
redhat/bind9.16<32:9.16.23-0.9.el8.1
32:9.16.23-0.9.el8.1
redhat/bind<32:9.16.23-5.el9_1
32:9.16.23-5.el9_1
ISC BIND>=9.16.11<9.16.27
ISC BIND>=9.16.11<9.16.27
ISC BIND>=9.17.0<=9.18.0
Fedoraproject Fedora=34
Fedoraproject Fedora=35
Fedoraproject Fedora=36
Netapp Baseboard Management Controller H300s Firmware
Netapp Baseboard Management Controller H300s
Netapp Baseboard Management Controller H500s Firmware
Netapp Baseboard Management Controller H500s
Netapp Baseboard Management Controller H700s Firmware
Netapp Baseboard Management Controller H700s
Netapp Baseboard Management Controller H300e Firmware
Netapp Baseboard Management Controller H300e
Netapp Baseboard Management Controller H500e Firmware
Netapp Baseboard Management Controller H500e
Netapp Baseboard Management Controller H700e Firmware
Netapp Baseboard Management Controller H700e
Netapp Baseboard Management Controller H410s Firmware
Netapp Baseboard Management Controller H410s
Netapp Baseboard Management Controller H410c Firmware
Netapp Baseboard Management Controller H410c
Siemens Sinec Ins<1.0
Siemens Sinec Ins=1.0
Siemens Sinec Ins=1.0-sp1
redhat/bind<9.16.27
9.16.27
redhat/bind<9.18.1
9.18.1
All of
Netapp H300s Firmware
Netapp H300s
All of
Netapp H500s Firmware
Netapp H500s
All of
Netapp H700s Firmware
Netapp H700s
All of
Netapp H300e Firmware
Netapp H300e
All of
Netapp H500e Firmware
Netapp H500e
All of
Netapp H700e Firmware
Netapp H700e
All of
Netapp H410s Firmware
Netapp H410s
All of
Netapp H410c Firmware
Netapp H410c

Remedy

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

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 BIND vulnerability?

    The vulnerability ID for this BIND vulnerability is CVE-2022-0396.

  • What is the severity of CVE-2022-0396?

    The severity of CVE-2022-0396 is medium.

  • How does the BIND vulnerability affect the software?

    The BIND vulnerability affects versions 9.16.11 to 9.16.26, 9.17.0 to 9.18.0, and versions 9.16.11-S1 to 9.16.26-S1 of BIND Supported.

  • How can a remote attacker exploit CVE-2022-0396?

    A remote attacker can exploit CVE-2022-0396 by sending specially crafted TCP streams to consume TCP connection slots indefinitely.

  • What is the recommended remedy for CVE-2022-0396?

    The recommended remedy for CVE-2022-0396 is to update to BIND version 9.16.27 or 9.18.1 depending on the affected version.

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