SB2022031719 - Slackware Linux update for bind
Published: March 17, 2022
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 4 secuirty vulnerabilities.
1) Reachable Assertion (CVE-ID: CVE-2022-0667)
The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.
The vulnerability exists due to a reachable assertion when processing requests for DS records. A remote attacker can send a specially crafted DNS request for a DS record that needs to be forwarded and perform a denial of service (DoS) attack.
2) Reachable Assertion (CVE-ID: CVE-2022-0635)
The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.
The vulnerability exists due to a reachable assertion when processing DNS requests. A remote attacker can send a repeated patterns of specific queries to servers with DNSSEC-Validated Cache feature (synth-from-dnssec) enabled and cause an INSIST failure in query.c:query_dname which causes named to terminate unexpectedly.
3) Resource management error (CVE-ID: CVE-2022-0396)
The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.
The vulnerability exists due to improper management of internal resources within the application that allows TCP connection slots to be consumed for an indefinite time
frame via a specifically crafted TCP stream sent from a client. A remote attacker can initiate a specially crafted TCP stream that 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.
This issue can only be triggered on BIND servers which have 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.
4) Reliance on Reverse DNS Resolution for a Security-Critical Action (CVE-ID: CVE-2021-25220)
The vulnerability allows a remote attacker to poison DNS cache.
The vulnerability exists due to an error in DNS forwarder implementation. When using forwarders, bogus NS records supplied by, or via, those forwarders may be cached and used by named if it needs to recurse for any reason, causing it to obtain and pass on potentially incorrect answers. The cache could become poisoned with incorrect records leading to
queries being made to the wrong servers, which might also result in
false information being returned to clients.
Remediation
Install update from vendor's website.