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
Path to dependency file: /api/pacman-api-vulnerability/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.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.
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2021-45046 (High) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar
May 27, 2023
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar - autoclosed
Jun 16, 2023
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar - autoclosed
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar
Jun 21, 2023
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2021-45046 (Critical) detected in log4j-core-2.7.jar, log4j-core-2.9.0.jar
CVE-2021-45046 (Critical) detected in log4j-core-2.9.0.jar
Mar 3, 2024
CVE-2021-45046 - Critical Severity Vulnerability
Vulnerable Library - log4j-core-2.9.0.jar
The Apache Log4j Implementation
Library home page: https://www.apache.org/
Path to dependency file: /api/pacman-api-vulnerability/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar,/home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.9.0/log4j-core-2.9.0.jar
Dependency Hierarchy:
Found in HEAD commit: acf9a0620c1a37cee4f2896d71e1c3731c5c7b06
Found in base branch: master
Vulnerability Details
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
CVSS 3 Score Details (9.0)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://logging.apache.org/log4j/2.x/security.html
Release Date: 2021-12-14
Fix Resolution: 2.12.2
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: