CVE-2021-44832 (Medium) detected in log4j-core-2.8.2.jar

[mend-for-github.aaakk.us.kg]

CVE-2021-44832 - Medium Severity Vulnerability

Vulnerable Library - log4j-core-2.8.2.jar

The Apache Log4j Implementation

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

Dependency Hierarchy:

• ❌ log4j-core-2.8.2.jar (Vulnerable Library)

Found in HEAD commit: 8c55da57e6742a71db36a297b399eb3abb06431c

Found in base branch: master

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: org.apache.logging.log4j:log4j-core:2.3.2,2.12.4,2.17.1

---

⛑️ Automatic Remediation is available for this issue