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-2022-23302 (High) detected in log4j-1.2.9.jar, log4j-1.2.17.jar #146
Path to vulnerable library: /sdk/resourcemanager/azure-resourcemanager-samples/src/main/resources/coffeeshop/webapps/coffeeshop/WEB-INF/lib/log4j-1.2.9.jar
Path to vulnerable library: /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
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2022-23302 - High Severity Vulnerability
log4j-1.2.9.jar
Path to vulnerable library: /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: /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
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Publish Date: 2022-01-18
URL: CVE-2022-23302
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://reload4j.qos.ch/
Release Date: 2022-01-18
Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1
Step up your Open Source Security Game with Mend here