遠端 Redhat Enterprise Linux 6/8 主機上安裝的套件受到 RHSA-2020: 3817 公告中所提及的多個弱點影響。

  - jackson-databind：org.apache.openjpa.ee.WASRegistryManagedRuntime 中的序列化小工具 (CVE-2020-11113)

  - wildfly：某些 EJB 交易物件可能累積，從而造成拒絕服務 (CVE-2020-14297)

  - wildfly：收到回應後，可能無法正確移除 EJB SessionOpenInvocations，進而造成拒絕服務 (CVE-2020-14307)

  - log4j：SMTP 附加器中與主機不相符的憑證驗證錯誤 (CVE-2020-9488)

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

遠端 Debian 9 主機上安裝的套件受 dla-2852 公告中提及的多個弱點影響。

  - Apache Log4j SMTP 附加器中存在不當驗證與主機不相符的憑證錯誤。該錯誤允許 SMTPS 連線遭攔截式攻擊攔截，進而洩漏透過該附加程式傳送的任何記錄訊息。(CVE-2020-9488)

  - Apache Log4j2 2.0-alpha1 版至 2.16.0 版 (不包括 2.12.3) 未能防止自我參照查閱的不受控制遞回。這會允許可控制執行緒內容對應資料的攻擊者在解譯特製字串時造成拒絕服務。此問題已在 Log4j 2.17.0 版和 2.12.3 版中修正。(CVE-2021-45105)

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

遠端主機受到 GLSA-202402-16 中所述的弱點影響 (Apache Log4j：多個弱點)

  - Log4j 1.2 中包含的一個 SocketServer 類別，此類別容易受到將未受信任資料還原序列化的影響，在接聽記錄資料的未受信任網路流量時，若與還原序列化小工具結合，惡意人士可能會惡意利用未受信任資料來從遠端執行任意程式碼。這會影響到 1.2 至 1.2.17 的 Log4j 版本。
    (CVE-2019-17571)

  - Apache Log4j SMTP 附加器中存在不當驗證與主機不相符的憑證錯誤。該錯誤允許 SMTPS 連線遭到攔截式攻擊攔截，進而洩漏透過該附加程式傳送的任何記錄訊息。已在 Apache Log4j 2.12.3 和 2.13.1 中修正 (CVE-2020-9488)

  - 在 2.1.0 之前的 Apache Chainsaw 版本中發現一個還原序列化缺陷，可導致惡意程式碼執行。(CVE-2020-9493)

  - 當攻擊者具有 Log4j 組態的寫入存取權，或組態參照攻擊者有權存取的 LDAP 服務時，所有 Log4j 1.x 版本中的 JMSSink 都容易受到未受信任資料的還原序列化影響。攻擊者可藉助提供 TopicConnectionFactoryBindingName 組態，造成 JMSSink 以與 CVE-2021-4104 類似的方式執行可導致遠端程式碼執行情形的 JNDI 要求。請注意，此問題只會在特別設定為使用 JMSSink (非預設) 時影響 Log4j 1.x。Apache Log4j 1.2 已於 2015 年 8 月結束其生命週期。使用者應升級至 Log4j 2，因為該版本可解決先前版本中的許多其他問題。(CVE-2022-23302)

  - 根據設計，Log4j 1.2.x 中的 JDBCAppender 接受 SQL 陳述式做為組態參數，其中要插入的值是來自 PatternLayout 的轉換器。此情形可能一律包含訊息轉換器 %m。攻擊者可藉此將建構的字串輸入已記錄應用程式的輸入欄位或標頭，進而透過允許執行非預期的 SQL 查詢來操控 SQL。請注意，此問題只會在特別設定為使用 JDBCAppender (非預設) 時影響 Log4j 1.x。
    從 2.0-beta8 版開始，JDBCAppender 重新引入，可適當支援參數化 SQL 查詢，並進一步自訂記錄中的欄位。Apache Log4j 1.2 已於 2015 年 8 月結束其生命週期。使用者應升級至 Log4j 2，因為該版本可解決先前版本中的許多其他問題。(CVE-2022-23305)

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

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

  - 當攻擊者具有 Log4j 組態的寫入存取權時，Log4j 1.2 中的 JMSAppender 容易受到不受信任資料之還原序列化的影響。攻擊者可藉助提供 TopicBindingName 和 TopicConnectionFactoryBindingName 組態，造成 JMSAppender 以與 CVE-2021-44228 類似的方式執行導致遠端程式碼執行的 JNDI 要求。請注意，此問題只會在特別設定為使用 JMSAppender (非預設) 時影響 Log4j 1.2。Apache Log4j 1.2 已於 2015 年 8 月結束其生命週期。使用者應升級至 Log4j 2，因為該版本可解決先前版本中的許多其他問題。(CVE-2021-4104)

  據發現，在某些非預設組態中，對 Apache Log4j CVE-2021-44228 中位址 2.15.0 的修正不完整。當記錄組態使用具有內容查閱的非預設模式配置 (例如，$${ctx:loginId}) 或執行緒內容對應模式 (%X、%mdc 或 %MDC)，對執行緒內容映射 (MDC) 具有控制權的攻擊者可藉此使用 JNDI Lookup 模式特製惡意輸入資料，進而在某些環境下洩露資訊和執行遠端程式碼，並且在所有環境下執行本機程式碼。Log4j 2.16.0 (Java 8) 和 Log4j 2.12.2 (Java 7) 可透過移除對訊息查閱模式的支援並預設停用 JNDI 功能來修正此問題。
    (CVE-2021-45046)

  - 在 Log4j2 2.0-beta9 2.15.0 及更早版本 (安全性版本 2.12.2、 2.12.3 和 2.3.1 除外) 中， 組態、記錄訊息和參數中使用的 JNDI 功能無法防範受攻擊者控制的 LDAP 和其他 JNDI 相關端點。若攻擊者能夠控制記錄訊息或記錄訊息參數，則可在啟用訊息查閱替代時，執行從 LDAP 伺服器載入的任意程式碼。自 log4j 2.15.0 開始，此行為已預設為停用。自 2.16.0 版 (以及 2.12.2、2.12.3 和 2.3.1 版) 開始，此功能已完全移除。請注意，此弱點為 log4j-core 特有，不會影響 log4net、log4cxx 或其他 Apache Logging Services 專案。
    (CVE-2021-44228)

  在 2.9.5 之前 (如 10 之前的 Apple iOS、10.12 之前的 OS X、10 之前的 tvOS 和 3 之前的 watchOS 及其他產品中所使用) 的 libxml2 中，xpointer.c 未在 XPointer 範圍中禁止命名空間節點，遠端攻擊者因而得以透過特製 XML 文件執行任意程式碼，或造成拒絕服務 (釋放後使用和記憶體損毀)。(CVE-2016-4658)

  - 3.73 或 3.68.1 ESR 之前版本的 NSS (網路安全性服務) 版本在處理 DER 編碼的 DSA 或 RSA-PSS 簽章時，容易受到堆積溢位的影響。使用 NSS 處理在 CMS、S/MIME、PKCS \#7 或 PKCS \#12 內編碼之簽章的應用程式可能會受此影響。使用 NSS 進行憑證驗證或其他 TLS、X.509、OCSP 或 CRL 功能的應用程式可能會受此影響，具體視該等應用程序設定 NSS 的方式而定。*注意：此弱點不會影響 Mozilla Firefox。* 但是，使用 NSS 進行簽章驗證的電子郵件用戶端和 PDF 檢視器 (例如 Thunderbird、LibreOffice、Evolution 和 Evince)，據信會受到影響。此弱點會影響 3.73 和 3.68.1 之前版本的 NSS。
    (CVE-2021-43527)

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an     SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent     through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1 (CVE-2020-9488)

Note that Nessus relies on the presence of the package as reported by the vendor.

The 16.1-16.2, 17.7-17.12, 18.8, and 19.12 versions of Primavera Unifier installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2020 CPU advisory.

  - Vulnerability in the Primavera Unifier product of Oracle Construction and Engineering (component: Platform     (Apache Derby)). Supported versions that are affected are 16.1-16.2, 17.7-17.12, 18.8 and 19.12. Easily     exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise     Primavera Unifier. Successful attacks of this vulnerability can result in unauthorized access to critical     data or complete access to all Primavera Unifier accessible data and unauthorized ability to cause a hang     or frequently repeatable crash (complete DOS) of Primavera Unifier. (CVE-2015-1832)

  - Vulnerability in the Primavera Unifier product of Oracle Construction and Engineering (component: Platform     (iText)). Supported versions that are affected are 16.1-16.2, 17.7-17.12, 18.8 and 19.12. Easily     exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise     Primavera Unifier. Successful attacks require human interaction from a person other than the attacker.
    Successful attacks of this vulnerability can result in takeover of Primavera Unifier. (CVE-2017-9096)

  - Vulnerability in the Primavera Unifier product of Oracle Construction and Engineering (component: Platform     (Apache Solr)). Supported versions that are affected are 16.1-16.2, 17.7-17.12, 18.8 and 19.12. Difficult     to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise     Primavera Unifier. Successful attacks of this vulnerability can result in takeover of Primavera Unifier.
    (CVE-2019-17558)

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

The remote Redhat Enterprise Linux 6 / 7 / 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:3817 advisory.

    Red Hat AMQ Clients enable connecting, sending, and receiving messages over the AMQP 1.0 wire transport     protocol to or from AMQ Broker 6 and 7.

    This update provides various bug fixes and enhancements in addition to the client package versions     previously released on Red Hat Enterprise Linux 6, 7, and 8.

    Security Fix(es):

    * jackson-databind: Serialization gadgets in org.apache.openjpa.ee.WASRegistryManagedRuntime     (CVE-2020-11113)

    * wildfly: Some EJB transaction objects may get accumulated causing Denial of Service (CVE-2020-14297)

    * wildfly: EJB SessionOpenInvocations may not be removed properly after a response is received causing     Denial of Service (CVE-2020-14307)

    * log4j: improper validation of certificate with host mismatch in SMTP appender (CVE-2020-9488)

    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.

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

  - JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write     access to the Log4j configuration. The attacker can provide TopicBindingName and     TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result     in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2     when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of     life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the     previous versions. (CVE-2021-4104)

  - It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-     default configurations. This could allows attackers with control over Thread Context Map (MDC) input data     when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for     example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input     data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some     environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix     this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
    (CVE-2021-45046)

  - Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI     features used in configuration, log messages, and parameters do not protect against attacker controlled     LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters     can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From     log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3,     and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to     log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
    (CVE-2021-44228)

  - xpointer.c in libxml2 before 2.9.5 (as used in Apple iOS before 10, OS X before 10.12, tvOS before 10, and     watchOS before 3, and other products) does not forbid namespace nodes in XPointer ranges, which allows     remote attackers to execute arbitrary code or cause a denial of service (use-after-free and memory     corruption) via a crafted XML document. (CVE-2016-4658)

  - NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow     when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures     encoded within CMS, S/MIME, PKCS \#7, or PKCS \#12 are likely to be impacted. Applications using NSS for     certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how     they configure NSS. *Note: This vulnerability does NOT impact Mozilla Firefox.* However, email clients and     PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and     Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1.
    (CVE-2021-43527)

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 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-2852 advisory.

    Several security vulnerabilities were found in Apache Log4j2, a Logging Framework for Java, which could     lead to a denial of service or information disclosure. CVE-2020-9488 Improper validation of certificate     with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted     by a man-in-the-middle attack which could leak any log messages sent through that appender. CVE-2021-45105     Apache Log4j2 did not protect from uncontrolled recursion from self-referential lookups. This allows an     attacker with control over Thread Context Map data to cause a denial of service when a crafted string is     interpreted. For Debian 9 stretch, these problems have been fixed in version 2.12.3-0+deb9u1. We recommend     that you upgrade your apache-log4j2 packages. For the detailed security status of apache-log4j2 please     refer to its security tracker page at: https://security-tracker.debian.org/tracker/apache-log4j2 Further     information about Debian LTS security advisories, how to apply these updates to your system and frequently     asked questions can be found at: https://wiki.debian.org/LTS

Tenable has extracted the preceding description block directly from the Debian 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-202402-16 (Apache Log4j: Multiple Vulnerabilities)

  - Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data     which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when     listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
    (CVE-2019-17571)

  - Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an     SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent     through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1 (CVE-2020-9488)

  - A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious     code execution. (CVE-2020-9493)

  - JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker     has write access to the Log4j configuration or if the configuration references an LDAP service the     attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing     JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to     CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which     is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2     as it addresses numerous other issues from the previous versions. (CVE-2022-23302)

  - By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the     values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be     included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or     headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue     only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default.
    Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized     SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of     life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the     previous versions. (CVE-2022-23305)

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

The versions of Oracle Siebel CRM installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2021 CPU advisory.

  - Vulnerability in the Siebel Core - Automation product of Oracle Siebel CRM (component: Test Automation     (Eclipse Jetty)). Supported versions that are affected are 21.9 and prior. Easily exploitable     vulnerability allows unauthenticated attacker with network access via TLS to compromise Siebel Core -     Automation. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or     frequently repeatable crash (complete DOS) of Siebel Core - Automation. (CVE-2021-28165)

  - Vulnerability in the Siebel UI Framework product of Oracle Siebel CRM (component: EAI (Apache Tomcat)).
    Supported versions that are affected are 21.9 and prior. Easily exploitable vulnerability allows     unauthenticated attacker with network access via HTTP to compromise Siebel UI Framework. Successful     attacks of this vulnerability can result in unauthorized access to critical data or complete access to all     Siebel UI Framework accessible data. (CVE-2021-25122)

  - Vulnerability in the Siebel UI Framework product of Oracle Siebel CRM (component: EAI, SWSE (OpenSSL)).
    Supported versions that are affected are 21.9 and prior. Easily exploitable vulnerability allows     unauthenticated attacker with network access via TLS to compromise Siebel UI Framework. Successful attacks     of this vulnerability can result in unauthorized access to critical data or complete access to all Siebel     UI Framework accessible data. (CVE-2016-2183)

  - Vulnerability in the Siebel Apps - Marketing product of Oracle Siebel CRM (component: Marketing (Apache     Tomcat)). Supported versions that are affected are 21.9 and prior. Difficult to exploit vulnerability     allows low privileged attacker with logon to the infrastructure where Siebel Apps - Marketing executes to     compromise Siebel Apps - Marketing. Successful attacks of this vulnerability can result in takeover of     Siebel Apps - Marketing. (CVE-2020-9484)

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

远程主机上安装的 Enterprise Manager Base Platform 16.2.0-16.2.11、17.12.0-17.12.7、18.8.0-18.8.9 和 19.12.0-19.12.4 版本受到 2020 年 7 月 CPU 公告中提及的多个漏洞的影响。

  - Oracle Construction and Engineering 的 Primavera Gateway 产品存在漏洞（组件：Admin (Apache Ant)）。支持的版本中受影响的是 16.2.0-16.2.11 和 17.12.0-17.12.7。可轻松利用的漏洞允许未经身份验证的攻击者通过 HTTP 进行网络访问，从而破坏 Primavera Gateway。
    成功攻击此漏洞可导致接管 Primavera Gateway。

  - Oracle Construction and Engineering 的 Primavera Gateway 产品存在漏洞（组件：Admin (jQuery)）。支持的版本中受影响的是 16.2.0-16.2.11、17.12.0-17.12.7、18.8.0-18.8.9 和 19.12.0-19.12.4。可轻松利用的漏洞允许未经身份验证的攻击者通过 HTTP 进行网络访问，从而破坏 Primavera Gateway。除攻击者以外的他人进行交互是实现成功攻击的必要条件，尽管漏洞存在于 Primavera Gateway 中，但攻击也可能会严重影响其他产品。
    成功攻击此漏洞可导致在未经授权的情况下更新、插入或删除某些 Primavera Gateway 可访问数据的访问权限，以及对 Primavera Gateway 可访问数据子集进行未经授权的读取访问。

  - Oracle Construction and Engineering 的 Primavera Gateway 产品存在漏洞（组件：Admin (Log4j)）。
    支持的版本中受影响的是 16.2.0-16.2.11、17.12.0-17.12.7、18.8.0-18.8.9 和 19.12.0-19.12.4。
    难以利用的漏洞允许未经身份验证的攻击者通过 SMTPS 进行网络访问，从而危害 Primavera Gateway。成功攻击此漏洞可导致在未经授权的情况下读取访问 Primavera Gateway 的可访问数据子集。

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

远程主机上安装的 WebLogic Server 版本受到 2020 年 10 月 CPU 公告中提及的多个漏洞的影响。

  - Console 组件中存在一个不明漏洞。未经身份验证的远程攻击者可以通过 HTTP 访问网络，利用此问题破坏服务器。成功利用此漏洞进行攻击可导致接管 Oracle WebLogic Server。（CVE-2020-14750、CVE-2020-14882）

  - Core 组件中存在一个不明漏洞。未经身份验证的远程攻击者可利用此问题，通过 IIOP 和 T3 协议破坏服务器。成功利用此漏洞进行攻击可导致接管 Oracle WebLogic Server。(CVE-2020-14859)

  - Core 组件中存在一个不明漏洞。未经身份验证的远程攻击者可利用此问题，通过 IIOP 协议破坏服务器。成功利用此漏洞进行攻击可导致接管 Oracle WebLogic Server。(CVE-2020-14841)

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

远程主机上安装的 Oracle E-Business Suite 版本受到 2021 年 4 月 CPU 公告中提及的多个漏洞的影响。

  - Oracle E-Business Suite 的 Oracle Applications Framework 产品中存在一个漏洞（组件：
    Home page）。支持的版本中受影响的是 12.2.10。可轻松利用的漏洞允许未经身份验证攻击者通过 HTTP 进行网络访问，从而破坏 Oracle Applications Framework。
    成功利用此漏洞进行攻击可导致在未经授权的情况下创建、删除或修改关键数据或所有 Oracle Applications Framework 可访问数据的访问权限，以及未经授权即可访问关键数据或完整访问所有 Oracle Applications Framework 可访问数据。
    (CVE-2021-2200)

  - Oracle E-Business Suite 的 Oracle Marketing 产品中存在一个漏洞（组件：Marketing Administration）。支持的版本中受影响的是 12.2.7-12.2.10。可轻松利用的漏洞允许未经身份验证的攻击者通过 HTTP 进行网络访问，从而破坏 Oracle Marketing。成功利用此漏洞进行攻击可导致在未经授权的情况下创建、删除或修改关键数据或所有 Oracle Marketing 可访问数据的访问权限，以及未经授权即可访问关键数据或完整访问所有 Oracle Marketing 可访问数据。(CVE-2021-2205)

  - Oracle E-Business Suite 的 Oracle Email Center 产品中存在一个漏洞（组件：Message Display）。支持的版本中受影响的是 12.1.1-12.1.3 和 12.2.3-12.2.10。可轻松利用的漏洞允许低权限攻击者通过 HTTP 进行网络访问，从而破坏 Oracle Email Center。虽然漏洞位于 Oracle Email Center 中，但攻击也可能会严重影响其他产品。成功利用此漏洞进行攻击可导致在未经授权的情况下访问关键数据，或完全访问 Oracle Email Center 所有可访问数据，以及在未经授权的情况下更新、插入或删除某些 Oracle Email Center 可访问数据的访问权限。(CVE-2021-2209)

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

远程 Debian 10/11 主机上安装的程序包受到 dsa-5020 公告中提及的多个漏洞影响。

  - 未正确验证 Apache Log4j SMTP 附加程序中与主机不匹配的证书。这可允许中间人发动拦截 SMTPS 连接攻击，进而泄露通过该附加程序发送的任何日志消息。(CVE-2020-9488)

  - 在 2.14.1 及之前版本的 Apache Log4j2 中，配置、日志消息和参数所使用的 JNDI 功能无法防范由攻击者控制的 LDAP 和其他与 JNDI 相关的端点。若启用消息查找替换，拥有日志消息或日志消息参数控制权限的攻击者可执行从 LDAP 服务器加载的任意代码。自 log4j 2.15.0 版本开始，此行为已默认禁用。在以前的版本（高于 2.10）中，可通过将系统属性 log4j2.formatMsgNoLookups 设置为 true 或从类路径（例如：zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class）中删除 JndiLookup 类来缓解此行为。Java 8u121（请参阅 https://www.oracle.com/java/technologies/javase/8u121-relnotes.html）通过将 com.sun.jndi.rmi.object.trustURLCodebase 和 com.sun.jndi.cosnaming.object.trustURLCodebase 默认设置为 false 来防止远程代码执行漏洞。(CVE-2021-44228)

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
140747	RHEL 6/8：AMQ 用戶端 2.8.0 版本 (中等) (RHSA-2020: 3817)	Nessus	Red Hat Local Security Checks	2020/9/23	2024/11/7	high
156396	Debian DLA-2852-1：apache-log4j2 - LTS 安全性更新	Nessus	Debian Local Security Checks	2021/12/30	2025/1/24	low
190670	GLSA-202402-16：Apache Log4j：多個弱點	Nessus	Gentoo Local Security Checks	2024/2/18	2024/2/18	critical
164572	Nutanix AOS：多個弱點 (NXSA-AOS-6.1.1)	Nessus	Misc.	2022/9/1	2025/2/17	high
223593	Linux Distros Unpatched Vulnerability : CVE-2020-9488	Nessus	Misc.	2025/3/4	2025/9/10	low
141641	Oracle Primavera Unifier (Oct 2020 CPU)	Nessus	CGI abuses	2020/10/21	2023/4/25	critical
140747	RHEL 6 / 7 / 8 : AMQ Clients 2.8.0 Release (Moderate) (RHSA-2020:3817)	Nessus	Red Hat Local Security Checks	2020/9/23	2024/11/7	high
164572	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-6.1.1)	Nessus	Misc.	2022/9/1	2025/2/17	high
156396	Debian DLA-2852-1 : apache-log4j2 - LTS security update	Nessus	Debian Local Security Checks	2021/12/30	2025/1/24	low
190670	GLSA-202402-16 : Apache Log4j: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2024/2/18	2024/2/18	critical
212425	Oracle Siebel Server (October 2021 CPU)	Nessus	Misc.	2024/12/11	2024/12/12	high
138526	Oracle Primavera Gateway（2020 年 7 月 CPU）	Nessus	CGI abuses	2020/7/16	2025/1/24	critical
141807	Oracle WebLogic Server 多个漏洞（2020 年 10 月 CPU）	Nessus	Misc.	2020/10/22	2024/11/29	critical
148952	Oracle E-Business Suite 多个漏洞（2021 年 4 月 CPU）	Nessus	Misc.	2021/4/23	2024/11/28	high
156015	Debian DSA-5020-1：apache-log4j2 - 安全更新	Nessus	Debian Local Security Checks	2021/12/12	2025/1/24	critical

偵測

搜尋 Plugin

high

low

critical

high

low

critical

high

high

low

critical

high

critical

critical

high

critical