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
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 - Critical Severity Vulnerability
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)
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)
Found in base branch: main
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.
Publish Date: 2021-12-14
URL: CVE-2021-45046
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - 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-14
Fix Resolution: 2.16.0
Step up your Open Source Security Game with Mend here