Path to vulnerable library: /sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar,/sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar,/sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar
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 - Critical Severity Vulnerability
log4j-core-2.14.1.jar
The Apache Log4j Implementation
Library home page: https://www.apache.org/
Path to dependency file: /auth-utils/jclient/pom.xml
Path to vulnerable library: /sitory/org/apache/logging/log4j/log4j-core/2.14.1/log4j-core-2.14.1.jar
Dependency Hierarchy: - :x: **log4j-core-2.14.1.jar** (Vulnerable Library)
log4j-core-2.13.2.jar
The Apache Log4j Implementation
Library home page: https://www.apache.org/
Path to dependency file: /auth/server/pom.xml
Path to vulnerable library: /sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar,/sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar,/sitory/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar
Dependency Hierarchy: - :x: **log4j-core-2.13.2.jar** (Vulnerable Library)
Found in base branch: main
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.
Publish Date: 2021-12-10
URL: CVE-2021-44228
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://logging.apache.org/log4j/2.x/security.html
Release Date: 2021-12-10
Fix Resolution: 2.15.0
Step up your Open Source Security Game with Mend here