The version of java-1.8.0-amazon-corretto installed on the remote host is prior to 1.8.0_312.b07-2. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2CORRETTO8-2021-001 advisory.

    No versions of an Amazon Linux Java Virtual Machine (JVM) are affected by CVE-2021-44228 or     CVE-2021-45046. However, if customers load a log4j version that is affected by CVE-2021-44228 or     CVE-2021-45046 into an Amazon Linux JVM, it will introduce the issues identified in CVE-2021-44228 and     CVE-2021-45046 into the JVM. This update modifies Amazon Linux packages that provide a JVM to also install     the AWS-developed hotpatch to mitigate CVE-2021-44228 or CVE-2021-45046 by default. For more information     on the hotpatch package in Amazon Linux, see https://alas.aws.amazon.com/announcements/2021-001.html

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.

According to its self-reported version, Cisco Unified Intelligence Center is affected by a remote code execution vulnerability.

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

Please see the included Cisco BID and Cisco Security Advisory for more information.

The version of log4j installed on the remote host is prior to 2.17.2-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-225 advisory.

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

  - Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are     vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI     LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by     limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
    (CVE-2021-44832)

  - 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 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) 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. This issue was fixed     in Log4j 2.17.0, 2.12.3, and 2.3.1. (CVE-2021-45105)

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

It is, therefore, affected by a vulnerability as referenced in the ALAS2022-2021-003 advisory.

    A flaw was found in the Java logging library Apache Log4j 2 in versions from 2.0-beta9 and before and     including 2.14.1. This could allow a remote attacker to execute code on the server if the system logs an     attacker-controlled string value with the attacker's JNDI LDAP server lookup. (CVE-2021-44228)

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
160410	Amazon Linux 2 : java-1.8.0-amazon-corretto (ALASCORRETTO8-2021-001)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/1/21	critical
161213	Cisco Unified Intelligence Center Log4j RCE	Nessus	CISCO	2022/5/16	2023/2/17	critical
168572	Amazon Linux 2022 : log4j (ALAS2022-2022-225)	Nessus	Amazon Linux Local Security Checks	2022/12/9	2024/12/11	critical
212468	Amazon Linux 2022 : log4j, log4j-jcl, log4j-slf4j (ALAS2022-2021-003)	Nessus	Amazon Linux Local Security Checks	2024/12/11	2024/12/12	critical

检测

插件搜索

critical

critical

critical

critical