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.

An update of the bindutils package has been released.

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the bind-9.16.23-9.el9 build changelog.

  - 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-3094)

  - 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-3736)

  - 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-3924)

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

According to the versions of the bind packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - 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-2795)

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

  - 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-3094)

  - 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-3736)

  - By spoofing the target resolver with responses that have a malformed ECDSA 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-2022-38177)

  - 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-2022-38178)

  - 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-3924)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2023-2792 advisory.

    - Handle subtle difference between upstream and rhel (CVE-2022-3094)
    - Prevent flooding with UPDATE requests (CVE-2022-3094)
    - Handle RRSIG queries when server-stale is active (CVE-2022-3736)
    - Fix crash when soft-quota is reached and serve-stale is active (CVE-2022-3924)
    - Bound the amount of work performed for delegations (CVE-2022-2795)
    - Fix possible serve-stale related crash (CVE-2022-3080)
    - Fix memory leak in ECDSA verify processing (CVE-2022-38177)

Tenable has extracted the preceding description block directly from the Oracle 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 AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2023:2792 advisory.

  - 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-2795)

  - 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-3094)

  - 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-3736)

  - 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-3924)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2792 advisory.

    The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols.
    BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing     with DNS); and tools for verifying that the DNS server is operating correctly.

    Security Fix(es):

    * bind: processing large delegations may severely degrade resolver performance (CVE-2022-2795)

    * bind: flooding with UPDATE requests may lead to DoS (CVE-2022-3094)

    * bind: sending specific queries to the resolver may cause a DoS (CVE-2022-3736)

    * bind: sending specific queries to the resolver may cause a DoS (CVE-2022-3924)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.8 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2023-2261 advisory.

    - Handle subtle difference between upstream and rhel (CVE-2022-3094)
    - Prevent flooding with UPDATE requests (CVE-2022-3094)
    - Handle RRSIG queries when server-stale is active (CVE-2022-3736)
    - Fix crash when soft-quota is reached and serve-stale is active (CVE-2022-3924)
    - Bound the amount of work performed for delegations (CVE-2022-2795)

Tenable has extracted the preceding description block directly from the Oracle 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 AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2023:2261 advisory.

  - 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-2795)

  - 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-3094)

  - 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-3736)

  - 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-3924)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2261 advisory.

    The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols.
    BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing     with DNS); and tools for verifying that the DNS server is operating correctly.

    Security Fix(es):

    * bind: processing large delegations may severely degrade resolver performance (CVE-2022-2795)

    * bind: flooding with UPDATE requests may lead to DoS (CVE-2022-3094)

    * bind: sending specific queries to the resolver may cause a DoS (CVE-2022-3736)

    * bind: sending specific queries to the resolver may cause a DoS (CVE-2022-3924)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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.

According to the versions of the bind packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - 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-3094)

  - 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-3736)

  - 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-3924)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-161 advisory.

    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-2795)

    A flaw was found in the Bind package, where the resolver can crash when stale cache and stale answers are     enabled, option stale-answer-client-timeout is set to 0 and there is a stale CNAME in the cache for an     incoming query. By sending specific queries to the resolver, an attacker can cause named to crash.
    (CVE-2022-3080)

    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-3094)

    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. (CVE-2022-3488)

    A flaw was found in Bind, where a resolver crash is possible. When stale cache and stale answers are     enabled, the option stale-answer-client-timeout is set to a positive integer, and the resolver receives an     RRSIG query. (CVE-2022-3736)

    By spoofing the target resolver with responses that have a malformed ECDSA 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-2022-38177)

    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-2022-38178)

    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-3924)

Tenable has extracted the preceding description block directly from the tested product 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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:0341-1 advisory.

  - 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-3094)

  - 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-3736)

  - 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-3924)

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

The remote Fedora 36 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2023-a3d608daf4 advisory.

    - [Release notes](https://downloads.isc.org/isc/bind9/9.16.37/RELEASE-NOTES-bind-9.16.37.html)

Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 37 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2023-95d98f89a8 advisory.

    - [Release notes](https://downloads.isc.org/isc/bind9/9.18.11/RELEASE-NOTES-bind-9.18.11.html)


Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 38 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2023-f1accd4b37 advisory.

    - [Release notes](https://downloads.isc.org/isc/bind9/9.18.11/RELEASE-NOTES-bind-9.18.11.html)

Tenable has extracted the preceding description block directly from the Fedora 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 Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5329 advisory.

  - 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-3094)

  - 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-3736)

  - 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-3924)

Note that Nessus has not tested for these issues 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-3924 advisory.

  - 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-3924)

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 bind installed on the remote host is prior to 9.16.37 / 9.18.11. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2023-025-01 advisory.

  - 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-3736)

  - 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-3094)

  - 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-3924)

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 20.04 LTS / 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5827-1 advisory.

    Rob Schulhof discovered that Bind incorrectly handled a large number of UPDATE messages. A remote attacker     could possibly use this issue to cause Bind to consume resources, resulting in a denial of service.
    (CVE-2022-3094)

    Borja Marcos discovered that Bind incorrectly handled certain RRSIG queries. A remote attacker could     possibly use this issue to cause Bind to crash, resulting in a denial of service. This issue only affected     Ubuntu 22.04 LTS and Ubuntu 22.10. (CVE-2022-3736)

    Maksym Odinintsev discovered that Bind incorrectly handled certain answers from stale cache. A remote     attacker could possibly use this issue to cause Bind to crash, resulting in a denial of service. This     issue only affected Ubuntu 22.04 LTS and Ubuntu 22.10. (CVE-2022-3924)

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

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

ID	Name	Product	Family	Severity
203971	Photon OS 3.0: Bindutils PHSA-2023-3.0-0538	Nessus	PhotonOS Local Security Checks	high
203177	Photon OS 4.0: Bindutils PHSA-2023-4.0-0340	Nessus	PhotonOS Local Security Checks	high
191422	CentOS 9 : bind-9.16.23-9.el9	Nessus	CentOS Local Security Checks	high
176840	EulerOS Virtualization 2.11.0 : bind (EulerOS-SA-2023-2105)	Nessus	Huawei Local Security Checks	high
176819	EulerOS Virtualization 2.11.1 : bind (EulerOS-SA-2023-2053)	Nessus	Huawei Local Security Checks	high
176273	Oracle Linux 8 : bind9.16 (ELSA-2023-2792)	Nessus	Oracle Linux Local Security Checks	medium
176151	AlmaLinux 8 : bind9.16 (ALSA-2023:2792)	Nessus	Alma Linux Local Security Checks	high
175854	RHEL 8 : bind9.16 (RHSA-2023:2792)	Nessus	Red Hat Local Security Checks	medium
175691	Oracle Linux 9 : bind (ELSA-2023-2261)	Nessus	Oracle Linux Local Security Checks	medium
175612	AlmaLinux 9 : bind (ALSA-2023:2261)	Nessus	Alma Linux Local Security Checks	high
175448	RHEL 9 : bind (RHSA-2023:2261)	Nessus	Red Hat Local Security Checks	medium
175253	EulerOS 2.0 SP11 : bind (EulerOS-SA-2023-1776)	Nessus	Huawei Local Security Checks	high
175245	EulerOS 2.0 SP11 : bind (EulerOS-SA-2023-1754)	Nessus	Huawei Local Security Checks	high
174579	Amazon Linux 2023 : bind, bind-chroot, bind-devel (ALAS2023-2023-161)	Nessus	Amazon Linux Local Security Checks	medium
171411	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : bind (SUSE-SU-2023:0341-1)	Nessus	SuSE Local Security Checks	high
171008	Fedora 36 : bind / bind-dyndb-ldap (2023-a3d608daf4)	Nessus	Fedora Local Security Checks	high
170868	Fedora 37 : bind / bind-dyndb-ldap (2023-95d98f89a8)	Nessus	Fedora Local Security Checks	high
170755	Fedora 38 : bind / bind-dyndb-ldap (2023-f1accd4b37)	Nessus	Fedora Local Security Checks	high
170726	Debian DSA-5329-1 : bind9 - security update	Nessus	Debian Local Security Checks	high
170682	ISC BIND 9.16.12 < 9.16.37 / 9.16.12-S1 < 9.16.37-S1 / 9.18.0 < 9.18.11 / 9.19.0 < 9.19.9 Assertion Failure (cve-2022-3924)	Nessus	DNS	high
170653	Slackware Linux 15.0 / current bind Multiple Vulnerabilities (SSA:2023-025-01)	Nessus	Slackware Local Security Checks	high
170632	Ubuntu 20.04 LTS / 22.04 LTS : Bind vulnerabilities (USN-5827-1)	Nessus	Ubuntu Local Security Checks	high

Detections

Analytics

CVE-2022-3924

high

Tenable Plugins

high

high

high

high

high

medium

high

medium

medium

high

medium

high

high

medium

high

high

high

high

high

high

high

high