The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:4094-1 advisory.

  - Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 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, 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)

  - 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 a denial of service (DOS) attack. Log4j 2.15.0 makes a best-     effort attempt to restrict JNDI LDAP lookups to localhost by default. Log4j 2.16.0 fixes this issue by     removing support for message lookup patterns and disabling JNDI functionality by default. (CVE-2021-45046)

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 java-1.6.0-openjdk installed on the remote host is prior to 1.6.0.41-1.13.13.1.78. The version of java-1.7.0-openjdk installed on the remote host is prior to 1.7.0.261-2.6.22.1.84. The version of java-1.8.0-openjdk installed on the remote host is prior to 1.8.0.312.b07-0.66. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2021-1553 advisory.

  - Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 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, 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)

  - 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 a denial of service (DOS) attack. Log4j 2.15.0 makes a best-     effort attempt to restrict JNDI LDAP lookups to localhost by default. Log4j 2.16.0 fixes this issue by     removing support for message lookup patterns and disabling JNDI functionality by default. (CVE-2021-45046)

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

A remote code execution vulnerability exists in VMWare vCenter in the bundled Apache Log4j logging library. Apache Log4j is vulnerable due to insufficient protections on message lookup substitutions when dealing with user controlled input. A remote, unauthenticated attacker can explolit this, via a web request, to execute arbitrary code with the permission level of the running Java process.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 515df85a-5cd7-11ec-a16d-001517a2e1a4 advisory.

  - Apache Log4j2 <=2.14.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. In previous     releases (>2.10) this behavior can be mitigated by setting system property log4j2.formatMsgNoLookups to     true or it can be mitigated in prior releases (<2.10) by removing the JndiLookup class from the     classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).
    (CVE-2021-44228)

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

A remote code execution vulnerability exists in Apache Log4j < 2.15.0 due to insufficient protections on message lookup substitutions when dealing with user controlled input. A remote, unauthenticated attacker can explolit this, via a web request to execute arbitrary code with the permission level of the running Java process.

This plugin sends a test string to a set of open ports on the target host. This plugin requires that both the scanner and target machine have internet access.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 1ea05bb8-5d74-11ec-bb1e-001517a2e1a4 advisory.

  - Apache Log4j2 <=2.14.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. In previous     releases (>2.10) this behavior can be mitigated by setting system property log4j2.formatMsgNoLookups to     true or it can be mitigated in prior releases (<2.10) by removing the JndiLookup class from the     classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).
    (CVE-2021-44228)

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

The remote host appears to be running UPnP. UPnP itself is not vulnerable to Log4Shell; however, the UPnP server could potentially be affected if it attempts to log data via a vulnerable log4j library.

This plugin requires that both the scanner and target machine have internet access.

A remote code execution vulnerability exists in MobileIron Core in the bundled Apache Log4j logging library.
Apache Log4j is vulnerable due to insufficient protections on message lookup substitutions when dealing with user controlled input. A remote, unauthenticated attacker can exploit this, via a web request, to execute arbitrary code with the permission level of the running Java process.

This plugin requires that both the scanner and target machine have internet access.

The remote Debian 10 / 11 host has a package installed that is affected by multiple vulnerabilities as referenced in the dsa-5020 advisory.

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

  - Apache Log4j2 <=2.14.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. In previous     releases (>2.10) this behavior can be mitigated by setting system property log4j2.formatMsgNoLookups to     true or by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar     org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121 (see     https://www.oracle.com/java/technologies/javase/8u121-relnotes.html) protects against remote code     execution by defaulting com.sun.jndi.rmi.object.trustURLCodebase and     com.sun.jndi.cosnaming.object.trustURLCodebase to false. (CVE-2021-44228)

Note that Nessus has not tested for this issue 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 a vulnerability as referenced in the dla-2842 advisory.

  - Apache Log4j2 <=2.14.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. In previous     releases (>2.10) this behavior can be mitigated by setting system property log4j2.formatMsgNoLookups to     true or it can be mitigated in prior releases (<2.10) by removing the JndiLookup class from the     classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).
    (CVE-2021-44228)

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 FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 3fadd7e4-f8fb-45a0-a218-8fd6423c338f advisory.

  - Apache Log4j2 <=2.14.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. In previous     releases (>2.10) this behavior can be mitigated by setting system property log4j2.formatMsgNoLookups to     true or by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar     org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121 (see     https://www.oracle.com/java/technologies/javase/8u121-relnotes.html) protects against remote code     execution by defaulting com.sun.jndi.rmi.object.trustURLCodebase and     com.sun.jndi.cosnaming.object.trustURLCodebase to false. (CVE-2021-44228)

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

ID	Name	Product	Family	Published	Updated	Severity
156153	openSUSE 15 Security Update : log4j (openSUSE-SU-2021:4094-1)	Nessus	SuSE Local Security Checks	12/17/2021	5/1/2023	critical
156174	Amazon Linux AMI : java-1.8.0-openjdk, java-1.7.0-openjdk, java-1.6.0-openjdk (ALAS-2021-1553)	Nessus	Amazon Linux Local Security Checks	12/18/2021	5/1/2023	critical
156035	VMware vCenter Log4Shell Direct Check (CVE-2021-44228) (VMSA-2021-0028)	Nessus	Misc.	12/13/2021	7/31/2024	critical
156052	FreeBSD : bastillion -- log4j vulnerability (515df85a-5cd7-11ec-a16d-001517a2e1a4)	Nessus	FreeBSD Local Security Checks	12/14/2021	11/6/2023	critical
156056	Apache Log4Shell RCE detection via Raw Socket Logging (Direct Check)	Nessus	Misc.	12/14/2021	7/17/2024	critical
156078	FreeBSD : serviio -- affected by log4j vulnerability (1ea05bb8-5d74-11ec-bb1e-001517a2e1a4)	Nessus	FreeBSD Local Security Checks	12/15/2021	11/6/2023	critical
156375	Apache Log4Shell RCE detection via callback correlation (Direct Check UPnP)	Nessus	Misc.	12/29/2021	7/17/2024	critical
156941	MobileIron Core Log4Shell Direct Check (CVE-2021-44228)	Nessus	Web Servers	1/21/2022	7/31/2024	critical
156015	Debian DSA-5020-1 : apache-log4j2 - security update	Nessus	Debian Local Security Checks	12/12/2021	2/17/2023	critical
156018	Debian DLA-2842-1 : apache-log4j2 - LTS security update	Nessus	Debian Local Security Checks	12/13/2021	2/17/2023	critical
156021	FreeBSD : graylog -- include log4j patches (3fadd7e4-f8fb-45a0-a218-8fd6423c338f)	Nessus	FreeBSD Local Security Checks	12/13/2021	11/6/2023	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical