遠端主機上安裝的 AOS 版本低於 5.16.1.3。因此，它受到 NXSA-AOS-5.16.1.3 公告中所提及的多個弱點影響。

  - 使用 Apache JServ Protocol (AJP) 時，信任連至 Apache Tomcat 的內傳連線時請務必謹慎。例如，Tomcat 認為 AJP 連線的可信度比類似的 HTTP 連線高。如果攻擊者可利用此類連線，這些連線就會以非正常的方式遭到惡意利用。在 Apache Tomcat 9.0.0.M1 至 9.0.0.30、8.5.0 至 8.5.50 和 7.0.0 至 7.0.99 中，Tomcat 出貨時已預設啟用會接聽所有已設定 IP 位址的 AJP 連接器。非必要時，此連接器應該 (安全性指南中也建議) 停用。此弱點報告指出了允許下列狀況發生的機制：- 從 Web 應用程式任意位置傳回任意檔案 - 將 Web 應用程式中的任何檔案處理成 JSP 此外，若 Web 應用程式允許檔案上傳並將這些檔案儲存在 Web 應用程式內 (或者攻擊者可利用其他方式控制 Web 應用程式的內容)，則加上將檔案處理為 JSP 的能力，即可能發生遠端程式碼執行。請務必注意，僅當非受信任使用者可存取 AJP 連接埠時，才需要執行減輕措施。若使用者希望採用深度防禦方式，並封鎖允許傳回任意檔案及以 JSP 形式執行的向量，可升級至 Apache Tomcat 9.0.31、8.5.51 或 7.0.100 或更新版本。9.0.31 版 AJP 連接器預設組態已做了一些變更，以強化預設組態。升級至 9.0.31、8.5.51 或 7.0.100 或更新版本的使用者可能需要微幅變更其組態。
    (CVE-2020-1938)

  - 在 5.3.6 及之前版本的 Linux 核心中，drivers/net/wireless/realtek/rtlwifi/ps.c 中的 rtl_p2p_noa_ie 缺少特定的上界檢查，從而造成緩衝區溢位。(CVE-2019-17666)

  - 5.1-rc5 之前的 Linux 核心允許 page->_refcount 參照計數溢位，若存在約 140 GiB 的 RAM，則會產生釋放後使用問題。這與 fs/fuse/dev.c、fs/pipe.c, fs/splice.c、include/linux/mm.h、include/linux/pipe_fs_i.h、kernel/trace/trace.c、mm/gup.c 和 mm/hugetlb.c 有關。FUSE 要求會發生此問題。(CVE-2019-11487)

  - 在 5.5 版之前的 Linux 上游核心版本中， 在 CVE-2019-11135 的修正程式中發現一個缺陷，Intel CPU 在處理推測性指令執行時會發生 TSX 非同步中止 (TAA) 錯誤。當客體在受 TAA 瑕疵 (TAA_NO = 0) 影響但未受 MDS 問題 (MDS_NO = 1) 影響的主機 CPU 上執行時，客體會使用 VERW 指令機制清除受影響的緩衝區。但是，將 MDS_NO = 1 位元匯出至客體時，客體並未使用 VERW 機制來清除受影響的緩衝區。此問題會影響在 Cascade Lake CPU 上執行的客體，且要求主機啟用「TSX」。此弱點對資料機密性造成的威脅最大。
    (CVE-2019-19338)

  - 2.20.0 版本之前 Python 適用的 Requests 套件會在收到相同主機名稱的 https 至 http 重新導向要求時，傳送 HTTP 授權標頭給 http URI，遠端攻擊者因而可以更輕鬆地藉由探查網路而找到憑證。(CVE-2018-18074)

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

遠端主機上安裝的 AOS 版本低於 5.17.1。因此，它受到 NXSA-AOS-5.17.1 公告中所提及的多個弱點影響。

  - 使用 Apache JServ Protocol (AJP) 時，信任連至 Apache Tomcat 的內傳連線時請務必謹慎。例如，Tomcat 認為 AJP 連線的可信度比類似的 HTTP 連線高。如果攻擊者可利用此類連線，這些連線就會以非正常的方式遭到惡意利用。在 Apache Tomcat 9.0.0.M1 至 9.0.0.30、8.5.0 至 8.5.50 和 7.0.0 至 7.0.99 中，Tomcat 出貨時已預設啟用會接聽所有已設定 IP 位址的 AJP 連接器。非必要時，此連接器應該 (安全性指南中也建議) 停用。此弱點報告指出了允許下列狀況發生的機制：- 從 Web 應用程式任意位置傳回任意檔案 - 將 Web 應用程式中的任何檔案處理成 JSP 此外，若 Web 應用程式允許檔案上傳並將這些檔案儲存在 Web 應用程式內 (或者攻擊者可利用其他方式控制 Web 應用程式的內容)，則加上將檔案處理為 JSP 的能力，即可能發生遠端程式碼執行。請務必注意，僅當非受信任使用者可存取 AJP 連接埠時，才需要執行減輕措施。若使用者希望採用深度防禦方式，並封鎖允許傳回任意檔案及以 JSP 形式執行的向量，可升級至 Apache Tomcat 9.0.31、8.5.51 或 7.0.100 或更新版本。9.0.31 版 AJP 連接器預設組態已做了一些變更，以強化預設組態。升級至 9.0.31、8.5.51 或 7.0.100 或更新版本的使用者可能需要微幅變更其組態。
    (CVE-2020-1938)

  - 在 5.3.6 及之前版本的 Linux 核心中，drivers/net/wireless/realtek/rtlwifi/ps.c 中的 rtl_p2p_noa_ie 缺少特定的上界檢查，從而造成緩衝區溢位。(CVE-2019-17666)

  - 5.1-rc5 之前的 Linux 核心允許 page->_refcount 參照計數溢位，若存在約 140 GiB 的 RAM，則會產生釋放後使用問題。這與 fs/fuse/dev.c、fs/pipe.c, fs/splice.c、include/linux/mm.h、include/linux/pipe_fs_i.h、kernel/trace/trace.c、mm/gup.c 和 mm/hugetlb.c 有關。FUSE 要求會發生此問題。(CVE-2019-11487)

  - 在 5.5 版之前的 Linux 上游核心版本中， 在 CVE-2019-11135 的修正程式中發現一個缺陷，Intel CPU 在處理推測性指令執行時會發生 TSX 非同步中止 (TAA) 錯誤。當客體在受 TAA 瑕疵 (TAA_NO = 0) 影響但未受 MDS 問題 (MDS_NO = 1) 影響的主機 CPU 上執行時，客體會使用 VERW 指令機制清除受影響的緩衝區。但是，將 MDS_NO = 1 位元匯出至客體時，客體並未使用 VERW 機制來清除受影響的緩衝區。此問題會影響在 Cascade Lake CPU 上執行的客體，且要求主機啟用「TSX」。此弱點對資料機密性造成的威脅最大。
    (CVE-2019-19338)

  - libxml2 2.9.1 中 xzlib.c 的 xz_decomp 函式未正確偵測壓縮錯誤，內容相依的攻擊者可藉此透過特別建構的 XML 資料，造成拒絕服務 (處理程序懸置)。
    (CVE-2015-8035)

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

An update of the apache package has been released.

This update includes a rebase from 9.0.13 up to 9.0.21 which resolves two CVEs along with various other bugs/features :

  - rhbz#1673856 tomcat-9.0.21 is available

  - rhbz#1713279 CVE-2019-0221 tomcat: XSS in SSI printenv

  - rhbz#1693326 CVE-2019-0199 tomcat: Apache Tomcat HTTP/2     DoS

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

The version of Tomcat installed on the remote host is prior to 9.0.16. It is, therefore, affected by a vulnerability as referenced in the fixed_in_apache_tomcat_9.0.16_security-9 advisory.

  - The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with     excessive numbers of SETTINGS frames and also permitted clients to keep streams open without     reading/writing request/response data. By keeping streams open for requests that utilised the Servlet     API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread     exhaustion and a DoS. (CVE-2019-0199)

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

This update for tomcat to version 9.0.21 fixes the following issues :

Security issues fixed :

  - CVE-2019-0199: Fixed a denial of service in the HTTP/2     implementation related to streams with excessive numbers     of SETTINGS frames (bsc#1131055).

  - CVE-2019-0221: Fixed a cross site scripting     vulnerability with the SSI printenv command     (bsc#1136085).

Non-security issues fixed :

  - Increase maximum number of threads and open files for     tomcat (bsc#1111966).

This update was imported from the SUSE:SLE-15-SP1:Update update project.

The version of AOS installed on the remote host is prior to 5.16.1.3. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-5.16.1.3 advisory.

  - When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to     Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP     connection. If such connections are available to an attacker, they can be exploited in ways that may be     surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped     with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected     (and recommended in the security guide) that this Connector would be disabled if not required. This     vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the     web application - processing any file in the web application as a JSP Further, if the web application     allowed file upload and stored those files within the web application (or the attacker was able to control     the content of the web application by some other means) then this, along with the ability to process a     file as a JSP, made remote code execution possible. It is important to note that mitigation is only     required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth     approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to     Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP     Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading     to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.
    (CVE-2020-1938)

  - rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux kernel through 5.3.6 lacks a     certain upper-bound check, leading to a buffer overflow. (CVE-2019-17666)

  - The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-     free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c,     include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hugetlb.c. It can     occur with FUSE requests. (CVE-2019-11487)

  - A flaw was found in the fix for CVE-2019-11135, in the Linux upstream kernel versions before 5.5 where,     the way Intel CPUs handle speculative execution of instructions when a TSX Asynchronous Abort (TAA) error     occurs. When a guest is running on a host CPU affected by the TAA flaw (TAA_NO=0), but is not affected by     the MDS issue (MDS_NO=1), the guest was to clear the affected buffers by using a VERW instruction     mechanism. But when the MDS_NO=1 bit was exported to the guests, the guests did not use the VERW mechanism     to clear the affected buffers. This issue affects guests running on Cascade Lake CPUs and requires that     host has 'TSX' enabled. Confidentiality of data is the highest threat associated with this vulnerability.
    (CVE-2019-19338)

  - The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon     receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover     credentials by sniffing the network. (CVE-2018-18074)

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 AOS installed on the remote host is prior to 5.17.1. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-5.17.1 advisory.

  - When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to     Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP     connection. If such connections are available to an attacker, they can be exploited in ways that may be     surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped     with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected     (and recommended in the security guide) that this Connector would be disabled if not required. This     vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the     web application - processing any file in the web application as a JSP Further, if the web application     allowed file upload and stored those files within the web application (or the attacker was able to control     the content of the web application by some other means) then this, along with the ability to process a     file as a JSP, made remote code execution possible. It is important to note that mitigation is only     required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth     approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to     Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP     Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading     to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.
    (CVE-2020-1938)

  - rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux kernel through 5.3.6 lacks a     certain upper-bound check, leading to a buffer overflow. (CVE-2019-17666)

  - The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-     free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c,     include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hugetlb.c. It can     occur with FUSE requests. (CVE-2019-11487)

  - A flaw was found in the fix for CVE-2019-11135, in the Linux upstream kernel versions before 5.5 where,     the way Intel CPUs handle speculative execution of instructions when a TSX Asynchronous Abort (TAA) error     occurs. When a guest is running on a host CPU affected by the TAA flaw (TAA_NO=0), but is not affected by     the MDS issue (MDS_NO=1), the guest was to clear the affected buffers by using a VERW instruction     mechanism. But when the MDS_NO=1 bit was exported to the guests, the guests did not use the VERW mechanism     to clear the affected buffers. This issue affects guests running on Cascade Lake CPUs and requires that     host has 'TSX' enabled. Confidentiality of data is the highest threat associated with this vulnerability.
    (CVE-2019-19338)

  - The xz_decomp function in xzlib.c in libxml2 2.9.1 does not properly detect compression errors, which     allows context-dependent attackers to cause a denial of service (process hang) via crafted XML data.
    (CVE-2015-8035)

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

現已提供適用於 Red Hat Enterprise Linux 6、Red Hat Enterprise Linux 7 與 Red Hat Enterprise Linux 8 的更新版 Red Hat JBoss Web Server 5.2.0 套件。Red Hat 產品安全性團隊已將此更新評等為具有中等安全性影響。可從〈參照〉一節的 CVE 連結中取得每個弱點之常見弱點評分系統 (CVSS) 的基本分數，其中包含有關嚴重性評等的詳細資訊。Red Hat JBoss Web Server 是一組已完全整合並經過認證的元件，可用於主控 Java Web 應用程式。它的組成元件有 Apache Tomcat Servlet 容器、JBoss HTTP Connector (mod_cluster)、適用於 Apache Tomcat 的 PicketLink Vault 延伸模組以及 Tomcat Native 程式庫。此 Red Hat JBoss Web Server 5.2 版本是 Red Hat JBoss Web Server 5.1 的替代項目，其中包含增強功能和元件升級項目，詳情請前往〈參照〉中的「版本資訊」連結。安全性修正：* openssl：SMT/Hyper-Threading 架構上的旁路弱點 (PortSmash) (CVE-2018-5407) * openssl：0 位元組記錄 padding oracle (CVE-2019-1559) * tomcat：寫入時的 HTTP/2 連線視窗耗盡，CVE-2019-0199 的修正不完整 (CVE-2019-10072) * tomcat：XSS 在 SSI printenv 中 (CVE-2019-0221) 如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

遠端主機上安裝的 Tomcat 版本比 8.5.38 舊。因此，會受到 fixed_in_apache_tomcat_8.5.38_security-8 公告中所提及的一個弱點影響。

  - Apache Tomcat 9.0.0.M1 至 9.0.14 版和 8.5.0 至 8.5.37 版的 HTTP/2 實作接受 SETTINGS 框架數過多的串流，也允許用戶端將串流保持開放狀態，而不讀取/寫入要求/回應資料。針對利用 Servlet API 封鎖 I/O 的要求將串流維持開放狀態，用戶端即可造成伺服器端執行緒封鎖，最終導致執行緒耗盡及 DoS。(CVE-2019-0199)

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

遠端主機上安裝的 AOS 版本低於 5.18。因此，它受到 NXSA-AOS-5.18 公告中所提及的多個弱點影響。

  - 使用 Apache JServ Protocol (AJP) 時，信任連至 Apache Tomcat 的內傳連線時請務必謹慎。例如，Tomcat 認為 AJP 連線的可信度比類似的 HTTP 連線高。如果攻擊者可利用此類連線，這些連線就會以非正常的方式遭到惡意利用。在 Apache Tomcat 9.0.0.M1 至 9.0.0.30、8.5.0 至 8.5.50 和 7.0.0 至 7.0.99 中，Tomcat 出貨時已預設啟用會接聽所有已設定 IP 位址的 AJP 連接器。非必要時，此連接器應該 (安全性指南中也建議) 停用。此弱點報告指出了允許下列狀況發生的機制：- 從 Web 應用程式任意位置傳回任意檔案 - 將 Web 應用程式中的任何檔案處理成 JSP 此外，若 Web 應用程式允許檔案上傳並將這些檔案儲存在 Web 應用程式內 (或者攻擊者可利用其他方式控制 Web 應用程式的內容)，則加上將檔案處理為 JSP 的能力，即可能發生遠端程式碼執行。請務必注意，僅當非受信任使用者可存取 AJP 連接埠時，才需要執行減輕措施。若使用者希望採用深度防禦方式，並封鎖允許傳回任意檔案及以 JSP 形式執行的向量，可升級至 Apache Tomcat 9.0.31、8.5.51 或 7.0.100 或更新版本。9.0.31 版 AJP 連接器預設組態已做了一些變更，以強化預設組態。升級至 9.0.31、8.5.51 或 7.0.100 或更新版本的使用者可能需要微幅變更其組態。
    (CVE-2020-1938)

  - 在 5.3.6 及之前版本的 Linux 核心中，drivers/net/wireless/realtek/rtlwifi/ps.c 中的 rtl_p2p_noa_ie 缺少特定的上界檢查，從而造成緩衝區溢位。(CVE-2019-17666)

  - 5.1-rc5 之前的 Linux 核心允許 page->_refcount 參照計數溢位，若存在約 140 GiB 的 RAM，則會產生釋放後使用問題。這與 fs/fuse/dev.c、fs/pipe.c, fs/splice.c、include/linux/mm.h、include/linux/pipe_fs_i.h、kernel/trace/trace.c、mm/gup.c 和 mm/hugetlb.c 有關。FUSE 要求會發生此問題。(CVE-2019-11487)

  - 在 5.5 版之前的 Linux 上游核心版本中， 在 CVE-2019-11135 的修正程式中發現一個缺陷，Intel CPU 在處理推測性指令執行時會發生 TSX 非同步中止 (TAA) 錯誤。當客體在受 TAA 瑕疵 (TAA_NO = 0) 影響但未受 MDS 問題 (MDS_NO = 1) 影響的主機 CPU 上執行時，客體會使用 VERW 指令機制清除受影響的緩衝區。但是，將 MDS_NO = 1 位元匯出至客體時，客體並未使用 VERW 機制來清除受影響的緩衝區。此問題會影響在 Cascade Lake CPU 上執行的客體，且要求主機啟用「TSX」。此弱點對資料機密性造成的威脅最大。
    (CVE-2019-19338)

  - libxml2 2.9.1 中 xzlib.c 的 xz_decomp 函式未正確偵測壓縮錯誤，內容相依的攻擊者可藉此透過特別建構的 XML 資料，造成拒絕服務 (處理程序懸置)。
    (CVE-2015-8035)

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

Apache Tomcat 中的預設 servlet 傳回目錄重新導向 (例如，當使用者要求 「/foo」時，重新導向至「/foo/」) 時，可利用特製的 URL 造成產生攻擊者所選任何 URI 的重新導向。(CVE-2018-11784) 在已啟用 enableCmdLineArguments 的 Windows 上執行時，Apache Tomcat 中的 CGI Servlet 容易受到一個遠端程式碼執行弱點影響，這是因為 JRE 將命令行引數傳遞至 Windows 的方式有錯誤所致。依預設，CGI Servlet 已停用。在 Tomcat 9.0.x 中，依預設，CGI 選項 enableCmdLineArguments 已停用 (為因應此弱點，在所有版本中，此選項預設均為停用狀態)。如需 JRE 行為的詳細說明，請參閱 Markus Wulftange 的網誌 (https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injec tions-in-windows.html) 以及此封存 MSDN 網誌 (https://web.archive.org/web/20161228144344/https://blogs.msdn.microso ft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command -line-arguments-the-wrong-way/)。(CVE-2019-0232) Apache Tomcat 的 HTTP/2 實作接受 SETTINGS 框架數過多的串流，也允許用戶端將串流保持開放狀態，而不讀取/寫入要求/回應資料。針對利用 Servlet API 封鎖 I/O 的要求將串流維持開放狀態，用戶端即可造成伺服器端執行緒封鎖，最終導致執行緒耗盡及 DoS。(CVE-2019-0199)

在 Tomcat servlet 和 JSP 引擎中發現數個問題，可導致工作階段固定攻擊、資訊洩漏、跨網站指令碼、透過資源耗盡造成拒絕服務，和不安全的重新導向。

The version of Tomcat installed on the remote host is prior to 9.0.16. It is, therefore, affected by a vulnerability as referenced in the fixed_in_apache_tomcat_9.0.16_security-9 advisory.

 - The HTTP/2 implementation accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS. (CVE-2019-0199)

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

The version of Tomcat installed on the remote host is prior to 8.5.41. It is, therefore, affected by a vulnerability as referenced in the fixed_in_apache_tomcat_8.5.41_security-8 advisory.

- The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write. By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS. (CVE-2019-10072)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
164582	Nutanix AOS：多個弱點 (NXSA-AOS-5.16.1.3)	Nessus	Misc.	2022/9/1	2025/2/17	critical
164612	Nutanix AOS：多個弱點 (NXSA-AOS-5.17.1)	Nessus	Misc.	2022/9/1	2025/9/1	critical
124862	Photon OS 1.0: Apache PHSA-2019-1.0-0227	Nessus	PhotonOS Local Security Checks	2019/5/14	2024/5/23	high
126225	Fedora 30 : 1:tomcat (2019-1a3f878d27)	Nessus	Fedora Local Security Checks	2019/6/25	2024/5/14	medium
126312	Apache Tomcat 9.0.0.M1 < 9.0.16	Nessus	Web Servers	2019/6/27	2024/5/23	high
127088	openSUSE Security Update : tomcat (openSUSE-2019-1808)	Nessus	SuSE Local Security Checks	2019/7/26	2024/5/8	medium
202870	Photon OS 2.0: Apache PHSA-2019-2.0-0153	Nessus	PhotonOS Local Security Checks	2024/7/22	2024/7/23	high
164582	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-5.16.1.3)	Nessus	Misc.	2022/9/1	2025/2/17	critical
164612	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-5.17.1)	Nessus	Misc.	2022/9/1	2025/9/1	critical
131214	RHEL 6 / 7 / 8：JBoss Web Server (RHSA-2019:3929)	Nessus	Red Hat Local Security Checks	2019/11/22	2025/2/21	high
197817	Apache Tomcat 8.5.0 < 8.5.38	Nessus	Web Servers	2024/5/23	2024/5/24	high
164595	Nutanix AOS：多個弱點 (NXSA-AOS-5.18)	Nessus	Misc.	2022/9/1	2025/9/1	critical
125294	Amazon Linux AMI : tomcat8 (ALAS-2019-1208)	Nessus	Amazon Linux Local Security Checks	2019/5/21	2025/2/27	high
132427	Debian DSA-4596-1：tomcat8 - 安全性更新	Nessus	Debian Local Security Checks	2019/12/30	2023/2/23	critical
700710	Apache Tomcat 9.0.x < 9.0.16 DoS	Nessus Network Monitor	Web Servers	2019/5/13	2019/5/13	high
700697	Apache Tomcat 8.5.x < 8.5.41 DoS Vulnerability	Nessus Network Monitor	Web Servers	2019/5/13	2019/5/13	high

检测

插件搜索

critical

critical

high

medium

high

medium

high

critical

critical

high

high

critical

high

critical

high

high