You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apache Log4j2 2.0-beta9 through 2.12.1 (excluding 2.3.1) and 2.13.0 through 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. From version 2.16.0 (for users requiring Java 8 or later), 2.12.2 (for Java 7 users), and 2.3.1 (for Java 6 users) 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.
If updating the package is an issue, you may remove the JndiLookup class from the classpath. The command to perform such action is: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class.
Additional Info Attack vector: NETWORK Attack complexity: LOW Confidentiality impact: HIGH Availability impact: HIGH Remediation Upgrade Recommendation: 2.3.2
The text was updated successfully, but these errors were encountered:
Checkmarx (SCA): Vulnerable Package
Vulnerability: Read More about CVE-2021-44228
Checkmarx Project: margaritalm/BookStore_Small_CLI_small
Repository URL: https://github.com/margaritalm/BookStore_Small_CLI_small
Branch: master
Scan ID: 79dde67e-447e-480d-9f9e-f0bfb2e3e6f8
Apache Log4j2 2.0-beta9 through 2.12.1 (excluding 2.3.1) and 2.13.0 through 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. From version 2.16.0 (for users requiring Java 8 or later), 2.12.2 (for Java 7 users), and 2.3.1 (for Java 6 users) 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.
How to remediate the Log4j RCE vulnerability?
The easiest and most recommended way to remediate this vulnerability is to update to log4j version 2.17.0 or later.
If updating the package is an issue, you may remove the JndiLookup class from the classpath. The command to perform such action is:
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
.Additional Info
Attack vector: NETWORK
Attack complexity: LOW
Confidentiality impact: HIGH
Availability impact: HIGH
Remediation Upgrade Recommendation: 2.3.2
The text was updated successfully, but these errors were encountered: