slf4j-log4j12-1.5.0.jar: 2 vulnerabilities (highest severity is: 9.8)

[dev-mend-for-github-com]

Vulnerable Library - slf4j-log4j12-1.5.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar

Found in HEAD commit: 5fcbcf42db4b6848b483f7c0d9a14f88a33779a8

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (slf4j-log4j12 version)	Remediation Available	Reachability
CVE-2019-17571	High	9.8	log4j-1.2.13.jar	Transitive	N/A*	❌
CVE-2022-23302	High	8.8	log4j-1.2.13.jar	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

Details

CVE-2019-17571

Vulnerable Library - log4j-1.2.13.jar

Log4j

Library home page: http://logging.apache.org/log4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar

Dependency Hierarchy:

• slf4j-log4j12-1.5.0.jar (Root Library)
  • ❌ log4j-1.2.13.jar (Vulnerable Library)

Found in HEAD commit: 5fcbcf42db4b6848b483f7c0d9a14f88a33779a8

Found in base branch: master

Reachability Analysis

The vulnerable code is not reachable.

Vulnerability Details

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

Publish Date: 2019-12-20

URL: CVE-2019-17571

CVSS 3 Score Details (9.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • 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://nvd.nist.gov/vuln/detail/CVE-2019-17571

Release Date: 2019-12-20

Fix Resolution: log4j:log4j - 1.2.13-NODEP,1.2.17-atlassian-1,1.2.16.redhat-5;org.slf4j:nlog4j - 1.2.18

CVE-2022-23302

Vulnerable Library - log4j-1.2.13.jar

Log4j

Library home page: http://logging.apache.org/log4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar

Dependency Hierarchy:

• slf4j-log4j12-1.5.0.jar (Root Library)
  • ❌ log4j-1.2.13.jar (Vulnerable Library)

Found in HEAD commit: 5fcbcf42db4b6848b483f7c0d9a14f88a33779a8

Found in base branch: master

Vulnerability Details

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

CVSS 3 Score Details (8.8)

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.

Suggested Fix

Type: Upgrade version

Origin: test

Release Date: 2022-01-18

Fix Resolution: test