prafullkotecha / azure-sdk-for-java

This repository is for active development of the Azure SDK for Java. For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/en-us/java/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-java.
MIT License
1 stars 0 forks source link

CVE-2021-44228 (High) detected in log4j-1.2.9.jar, log4j-1.2.17.jar - autoclosed #138

Closed mend-bolt-for-github[bot] closed 2 years ago

mend-bolt-for-github[bot] commented 2 years ago

CVE-2021-44228 - High Severity Vulnerability

Vulnerable Libraries - log4j-1.2.9.jar, log4j-1.2.17.jar

log4j-1.2.9.jar

Path to vulnerable library: azure-sdk-for-java/sdk/resourcemanager/azure-resourcemanager-samples/src/main/resources/coffeeshop/webapps/coffeeshop/WEB-INF/lib/log4j-1.2.9.jar

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

log4j-1.2.17.jar

Apache Log4j 1.2

Path to vulnerable library: azure-sdk-for-java/sdk/spring/azure-spring-data-gremlin/package/apache-tinkerpop-gremlin-server-minimal-3.3.4.tar/apache-tinkerpop-gremlin-server-minimal-3.3.4/lib/log4j-1.2.17.jar

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

Found in base branch: master

Vulnerability Details

Log4j versions prior to 2.15.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.

Publish Date: 2021-11-27

URL: CVE-2021-44228

CVSS 3 Score Details (10.0)

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.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

Release Date: 2021-12-10

Fix Resolution: org.apache.logging.log4j:log4j-core:2.15.0


Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 2 years ago

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.