On vulnerable configurations, the named daemon may, in some circumstances, terminate with an assertion failure. Vulnerable configurations are those that include a reference to http within the listen-on statements in their named.conf. TLS is used by both DNS over TLS (DoT) and DNS over HTTPS (DoH), but configurations using DoT alone are unaffected. Affects BIND 9.18.0 -> 9.18.2 and version 9.19.0 of the BIND 9.19 development branch.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0612 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2023-3341:
    The code that processes control channel messages sent to `named` calls certain functions recursively     during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on     the environment, this may cause the packet-parsing code to run out of available stack memory, causing     `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its     contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key;
    only network access to the control channel's configured TCP port is necessary.
    This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16,     9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

    CVE-2023-4236:
    A flaw in the networking code handling DNS-over-TLS queries may cause `named` to terminate unexpectedly     due to an assertion failure. This happens when internal data structures are incorrectly reused under     significant DNS-over-TLS query load.
    This issue affects BIND 9 versions 9.18.0 through 9.18.18 and 9.18.11-S1 through 9.18.18-S1.

    CVE-2022-38178:
    By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can     trigger a small memory leak. It is possible to gradually erode available memory to the point where named     crashes for lack of resources.

    CVE-2023-2828:
    Every `named` instance configured to run as a recursive resolver maintains a cache database holding the     responses to the queries it has recently sent to authoritative servers. The size limit for that cache     database can be configured using the `max-cache-size` statement in the configuration file; it defaults to     90% of the total amount of memory available on the host. When the size of the cache reaches 7/8 of the     configured limit, a cache-cleaning algorithm starts to remove expired and/or least-recently used RRsets     from the cache, to keep memory use below the configured limit.

    It has been discovered that the effectiveness of the cache-cleaning algorithm used in `named` can be     severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing     the configured `max-cache-size` limit to be significantly exceeded.
    This issue affects BIND 9 versions 9.11.0 through 9.16.41, 9.18.0 through 9.18.15, 9.19.0 through 9.19.13,     9.11.3-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1.

    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.

    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.

    CVE-2022-2795:
    By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the     resolver/'s performance, effectively denying legitimate clients access to the DNS resolution service.

    CVE-2022-2881:
    The underlying bug might cause read past end of the buffer and either read memory it should not read, or     crash the process.

    CVE-2022-2906:
    An attacker can leverage this flaw to gradually erode available memory to the point where named crashes     for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the     potential to deny service.

    CVE-2022-3080:
    By sending specific queries to the resolver, an attacker can cause named to crash.

    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.

    CVE-2022-1183:
    On vulnerable configurations, the named daemon may, in some circumstances, terminate with an assertion     failure. Vulnerable configurations are those that include a reference to http within the listen-on     statements in their named.conf. TLS is used by both DNS over TLS (DoT) and DNS over HTTPS (DoH), but     configurations using DoT alone are unaffected. Affects BIND 9.18.0 -> 9.18.2 and version 9.19.0 of the     BIND 9.19 development branch.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 22.04 LTS host has packages installed that are affected by a vulnerability as referenced in the USN-5429-1 advisory.

    Thomas Amgarten discovered that Bind incorrectly handled certain TLS connections being destroyed. A remote     attacker could possibly use this issue to cause Bind to crash, resulting in a denial of service.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of ISC BIND installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the cve-2022-1183 advisory.

  - An assertion failure can be triggered if a TLS connection to a configured http TLS listener with a defined     endpoint is destroyed too early.On vulnerable configurations, the named daemon may, in some circumstances,     terminate with an assertion failure.  Vulnerable configurations are those that include a reference to     http  within the  listen-on  statements in their  named.conf .  TLS is used by both DNS over TLS (DoT) and     DNS over HTTPS (DoH), but configurations using DoT alone are unaffected. (CVE-2022-1183)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
239987	TencentOS Server 4: bind (TSSA-2024:0612)	Nessus	Tencent Local Security Checks	medium
161336	Ubuntu 22.04 LTS : Bind vulnerability (USN-5429-1)	Nessus	Ubuntu Local Security Checks	high
161326	ISC BIND 9.18.0 < 9.18.3 Assertion Failure (cve-2022-1183)	Nessus	DNS	high

Detections

Analytics

CVE-2022-1183

high

Tenable Plugins

medium

high

high