There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

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

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

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

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

遠端 Ubuntu 18.04 LTS/20.04 LTS/22.04 LTS 主機上安裝的套件受到 USN-5626-1 公告中所提及的多個弱點影響。

  - 攻擊者可藉由讓利用此缺陷的查詢涌入目標解析器，來顯著降低解析器的效能，有效地拒絕合法用戶端存取 DNS 解析服務。
    (CVE-2022-2795)

  - 此基礎錯誤可能造成讀取時超出緩衝區末尾，並讀取不應讀取的記憶體，或造成處理程序損毀。(CVE-2022-2881)

  - 攻擊者可利用此缺陷造成可用記憶體逐漸減少，直到 named 因缺乏資源而當機。重新啟動後，攻擊者必須重新開始操作，但仍有可能觸發拒絕服務。(CVE-2022-2906)

  - 攻擊者可藉由向解析器傳送特定查詢來造成 named 損毀。(CVE-2022-3080)

  - 攻擊者可使用具有格式錯誤的 ECDSA 簽章的回應來欺騙目標解析器，進而觸發小型記憶體洩漏。這可能會導致可用記憶體逐漸減少，直到 named 因缺乏資源而當機。(CVE-2022-38177)

  - 攻擊者可使用具有格式錯誤的 EdDSA 簽章的回應來欺騙目標解析器，進而觸發小型記憶體洩漏。這可能會導致可用記憶體逐漸減少，直到 named 因缺乏資源而當機。(CVE-2022-38178)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機受到 GLSA-202210-25 中所述的弱點影響 (ISC BIND：多個弱點)

  - 在 BIND 9.3.0 -> 9.11.35、 9.12.0 -> 9.16.21，以及 BIND Supported Preview Edition 的 9.9.3-S1 -> 9.11.35-S1 和 9.16.8-S1 -> 9.16.21-S1 版中，以及 BIND 9.17 開發分支的發行版本 9.17.0 -> 9.17.18，利用回應處理程序中的瑕疵惡意利用損毀的授權伺服器可造成 BIND 解析器效能降低。lame 快取目前的設計方式使其內部資料結構幾乎可以無限增長，進而可能造成用戶端查詢處理嚴重延遲。(CVE-2021-25219)

  - BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND 受支援預覽版：BIND 9 9.1.0 之前的 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 版本 (包括支援的預覽版本) 也會受到影響，但尚未經過測試，原因是這些版本目前是 EOL。
    快取可能因不正確的記錄而遭到破壞，進而導致對錯誤的伺服器進行查詢，這也有可能導致將錯誤的資訊傳回給用戶端。(CVE-2021-25220)

  - BIND 9.16.11 -> 9.16.26、9.17.0 -> 9.18.0，以及 BIND 9.16.11-S1 -> 9.16.26-S1 受支援預覽版。特製的 TCP 串流可造成 BIND 連線無限期保持在 CLOSE_WAIT 狀態，即使在用戶端終止連線後也是如此。
    (CVE-2022-0396)

  - 攻擊者可藉由讓利用此缺陷的查詢涌入目標解析器，來顯著降低解析器的效能，有效地拒絕合法用戶端存取 DNS 解析服務。
    (CVE-2022-2795)

  - 此基礎錯誤可能造成讀取時超出緩衝區末尾，並讀取不應讀取的記憶體，或造成處理程序損毀。(CVE-2022-2881)

  - 攻擊者可利用此缺陷造成可用記憶體逐漸減少，直到 named 因缺乏資源而當機。重新啟動後，攻擊者必須重新開始操作，但仍有可能觸發拒絕服務。(CVE-2022-2906)

  - 攻擊者可藉由向解析器傳送特定查詢來造成 named 損毀。(CVE-2022-3080)

  - 攻擊者可使用具有格式錯誤的 ECDSA 簽章的回應來欺騙目標解析器，進而觸發小型記憶體洩漏。這可能會導致可用記憶體逐漸減少，直到 named 因缺乏資源而當機。(CVE-2022-38177)

  - 攻擊者可使用具有格式錯誤的 EdDSA 簽章的回應來欺騙目標解析器，進而觸發小型記憶體洩漏。這可能會導致可用記憶體逐漸減少，直到 named 因缺乏資源而當機。(CVE-2022-38178)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的 ISC BIND 版本比測試版本舊。因此，它受到 cve-2022-2906 公告中提及的一個弱點影響。

  - 攻擊者可利用此缺陷造成可用記憶體逐漸減少，直到 named 因缺乏資源而當機。重新啟動後，攻擊者必須重新開始操作，但仍有可能觸發拒絕服務。(CVE-2022-2906)

請注意，Nessus 並未測試此問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

远程 Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS 主机上安装的程序包受到 USN-5626-1 公告中提及的多个漏洞的影响。

  - 通过使用利用此缺陷的查询淹没目标解析器，攻击者可显着削弱解析器的性能，从而有效拒绝合法客户端对 DNS 解析服务的访问。
    (CVE-2022-2795)

  - 此底层缺陷可能导致读取时超过缓冲区末尾，并且读取不应读取的内存或导致进程崩溃。(CVE-2022-2881)

  - 攻击者可利用此缺陷逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。重新启动后，攻击者必须重新开始，但仍有可能造成程序拒绝服务。(CVE-2022-2906)

  - 通过向解析器发送特定查询，攻击者可造成 named 崩溃。(CVE-2022-3080)

  - 攻击者可通过使用具有格式错误的 ECDSA 签名的响应来欺骗目标解析器，从而触发小型内存泄漏。这可能会逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。(CVE-2022-38177)

  - 攻击者可通过使用具有格式错误的 EdDSA 签名的响应来欺骗目标解析器，从而触发小型内存泄漏。这可能会逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。(CVE-2022-38178)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

远程主机受到 GLSA-202210-25 中所述漏洞的影响（ISC BIND：多个漏洞）

  - 在 BIND 9.3.0 -> 9.11.35、9.12.0 -> 9.16.21 以及 BIND Supported Preview Edition 的 9.9.3-S1 -> 9.11.35-S1 和 9.16.8-S1 -> 9.16.21-S1 版本中，以及 BIND 9.17 开发分支的发行版本 9.17.0 -> 9.17.18 中，使用响应处理中的缺陷攻击损坏的授权服务器可导致 BIND 解析器性能下降。lame 缓存的当前设计方式使其内部数据结构几乎可以无限增长，这可能导致客户端查询处理显著延迟。(CVE-2021-25219)

  - BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> BIND 支持的预览版本 9.18.0：9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 低于所示的 BIND 9 版本（回退到 9.1.0 版本，包括 Supported Preview Edition 版本）据信也受到影响，但由于版本生命周期现已终结，因而尚未经过测试。
    缓存可能因错误的记录而中毒，从而导致查询错误的服务器，而这也可能导致客户端接收到错误的信息。 (CVE-2021-25220)

  - BIND 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0 和 9.16.11-S1 版本 -> BIND Supported Preview Edition 9.16.26-S1 版本。特别构建的 TCP 流可导致与 BIND 的连接无限期保持 CLOSE_WAIT 状态，即使在客户端终止连接之后也是如此。
    (CVE-2022-0396)

  - 通过使用利用此缺陷的查询淹没目标解析器，攻击者可显着削弱解析器的性能，从而有效拒绝合法客户端对 DNS 解析服务的访问。
    (CVE-2022-2795)

  - 此底层缺陷可能导致读取时超过缓冲区末尾，并且读取不应读取的内存或导致进程崩溃。(CVE-2022-2881)

  - 攻击者可利用此缺陷逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。重新启动后，攻击者必须重新开始，但仍有可能造成程序拒绝服务。(CVE-2022-2906)

  - 通过向解析器发送特定查询，攻击者可造成 named 崩溃。(CVE-2022-3080)

  - 攻击者可通过使用具有格式错误的 ECDSA 签名的响应来欺骗目标解析器，从而触发小型内存泄漏。这可能会逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。(CVE-2022-38177)

  - 攻击者可通过使用具有格式错误的 EdDSA 签名的响应来欺骗目标解析器，从而触发小型内存泄漏。这可能会逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。(CVE-2022-38178)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

远程主机上安装的 ISC BIND 的版本低于测试版本。因此，该应用程序受到 cve-2022-2906 公告中提及的漏洞的影响。

  - 攻击者可利用此缺陷逐渐消耗可用内存，直到 named 由于缺少资源而崩溃。重新启动后，攻击者必须重新开始，但仍有可能造成程序拒绝服务。(CVE-2022-2906)

请注意，Nessus 尚未测试此问题，而是只依据应用程序自我报告的版本号进行判断。

リモートの Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS ホストには、USN-5626-1 のアドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

  - この欠陥を悪用するクエリをターゲットリゾルバーに殺到させることで、攻撃者はリゾルバーのパフォーマンスを大幅に低下させ、正当なクライアントの DNS 解決サービスへのアクセスを効果的に拒否する可能性があります。
    (CVE-2022-2795)

  - 根本的なバグにより、バッファの終端を超えて読み取りが行われ、読み取られないはずのメモリが読み取られるか、プロセスがクラッシュする可能性があります。(CVE-2022-2881)

  攻撃者はこの欠陥を利用してリソースの不足により named がクラッシュするまで、利用可能なメモリが徐々に消費される可能性があります。攻撃者は再起動時に再び開始する必要がありますが、それでもサービスを拒否する可能性があります。(CVE-2022-2906)

  - リゾルバーに特定のクエリを送信することで、攻撃者が named をクラッシュさせる可能性があります。(CVE-2022-3080)

  - 無効な形式の ECDSA 署名を持つ応答でターゲットリゾルバーを偽装することで、攻撃者が小さなメモリリークを発生させる可能性があります。リソースの不足により named がクラッシュするまで、利用可能なメモリが徐々に消費される可能性があります。(CVE-2022-38177)

  - 無効な形式の EdDSA 署名を持つ応答でターゲットリゾルバーを偽装することで、攻撃者が小さなメモリリークを発生させる可能性があります。リソースの不足により named がクラッシュするまで、利用可能なメモリが徐々に消費される可能性があります。(CVE-2022-38178)

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションの自己報告されたバージョン番号にのみ依存しています。

リモートホストにインストールされている ISC BIND のバージョンは、テストバージョンより前のものです。したがって、cve-2022-2906 のアドバイザリに記載されている脆弱性の影響を受けます。

  攻撃者はこの欠陥を利用してリソースの不足により named がクラッシュするまで、利用可能なメモリが徐々に消費される可能性があります。攻撃者は再起動時に再び開始する必要がありますが、それでもサービスを拒否する可能性があります。(CVE-2022-2906)

Nessus はこの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存しています。

The remote Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5626-1 advisory.

    Yehuda Afek, Anat Bremler-Barr, and Shani Stajnrod discovered that Bind incorrectly handled large     delegations. A remote attacker could possibly use this issue to reduce performance, leading to a denial of     service. (CVE-2022-2795)

    It was discovered that Bind incorrectly handled statistics requests. A remote attacker could possibly use     this issue to obtain sensitive memory contents, or cause a denial of service. This issue only affected     Ubuntu 22.04 LTS. (CVE-2022-2881)

    It was discovered that Bind incorrectly handled memory when processing certain Diffie-Hellman key     exchanges. A remote attacker could use this issue to consume resources, leading to a denial of service.
    This issue only affected Ubuntu 22.04 LTS. (CVE-2022-2906)

    Maksym Odinintsev discovered that Bind incorrectly handled answers from cache when configured with a zero     stale-answer-timeout. 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. (CVE-2022-3080)

    It was discovered that Bind incorrectly handled memory when processing ECDSA DNSSEC verification. A remote     attacker could use this issue to consume resources, leading to a denial of service. This issue only     affected Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2022-38177)

    It was discovered that Bind incorrectly handled memory when processing EDDSA DNSSEC verification. A remote     attacker could use this issue to consume resources, leading to a denial of service. (CVE-2022-38178)

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.

The remote host is affected by the vulnerability described in GLSA-202210-25 (ISC BIND: Multiple Vulnerabilities)

  - In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 ->     9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND     9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing     can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it     possible for its internal data structures to grow almost infinitely, which may cause significant delays in     client query processing. (CVE-2021-25219)

  - BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 ->     9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including     Supported Preview Editions - are also believed to be affected but have not been tested as they are EOL.
    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. (CVE-2021-25220)

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

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

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

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

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

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

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 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 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-2906 advisory.

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

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
403666	Alpine: bind: security update to 9.16.33-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	2023/10/31	2026/7/2	medium
403666	Alpine: bind: security update to 9.16.33-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	2023/10/31	2026/7/2	medium
423727	Alpine: multiple bind packages: security update to 9.18.7-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	2025/4/4	2026/7/2	medium
423727	Alpine: multiple bind packages: security update to 9.18.7-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	2025/4/4	2026/7/2	medium
165290	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS：Bind 弱點 (USN-5626-1)	Nessus	Ubuntu Local Security Checks	2022/9/21	2025/9/3	medium
166720	GLSA-202210-25：ISC BIND：多個弱點	Nessus	Gentoo Local Security Checks	2022/10/31	2023/10/6	high
165302	ISC BIND 9.18.0 < 9.18.7 / 9.19.0 < 9.19.5 記憶體耗盡 (cve-2022-2906)	Nessus	DNS	2022/9/22	2023/1/26	high
165290	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS：Bind 漏洞 (USN-5626-1)	Nessus	Ubuntu Local Security Checks	2022/9/21	2025/9/3	medium
166720	GLSA-202210-25 : ISC BIND：多个漏洞	Nessus	Gentoo Local Security Checks	2022/10/31	2023/10/6	high
165302	ISC BIND 9.18.0 < 9.18.7 / 9.19.0 < 9.19.5 内存耗尽 (cve-2022-2906)	Nessus	DNS	2022/9/22	2023/1/26	high
165290	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : Bind の脆弱性 (USN-5626-1)	Nessus	Ubuntu Local Security Checks	2022/9/21	2025/9/3	medium
165302	ISC BIND 9.18.0 < 9.18.7 / 9.19.0 < 9.19.5 メモリ枯渇 (cve-2022-2906)	Nessus	DNS	2022/9/22	2023/1/26	high
165290	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : Bind vulnerabilities (USN-5626-1)	Nessus	Ubuntu Local Security Checks	2022/9/21	2025/9/3	medium
166720	GLSA-202210-25 : ISC BIND: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2022/10/31	2023/10/6	high
239987	TencentOS Server 4: bind (TSSA-2024:0612)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	medium
165302	ISC BIND 9.18.0 < 9.18.7 / 9.19.0 < 9.19.5 Memory Exhaustion (cve-2022-2906)	Nessus	DNS	2022/9/22	2023/1/26	high

偵測

搜尋 Plugin

medium

medium

medium

medium

medium

high

high

medium

high

high

medium

high

medium

high

medium

high