tabacmend / Java-Demo-old

Apache License 2.0
0 stars 0 forks source link

CVE-2021-44832 (Medium) detected in log4j-core-2.14.0.jar - autoclosed #73

Closed mend-for-github-com[bot] closed 1 year ago

mend-for-github-com[bot] commented 1 year ago

CVE-2021-44832 - Medium Severity Vulnerability

Vulnerable Library - log4j-core-2.14.0.jar

The Apache Log4j Implementation

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /pom.xml

Path to vulnerable library: /repository/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar

Dependency Hierarchy: - :x: **log4j-core-2.14.0.jar** (Vulnerable Library)

Found in HEAD commit: d59b9e6920cb030c011bf733ee2b5e6a2991433b

Found in base branch: log4j-fix

Vulnerability Details

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Publish Date: 2021-12-28

URL: CVE-2021-44832

CVSS 3 Score Details (6.6)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-28

Fix Resolution: 2.17.1


:rescue_worker_helmet: Automatic Remediation is available for this issue

mend-for-github-com[bot] commented 1 year ago

:heavy_check_mark: 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.