calcite-tutorial-common-1.0-SNAPSHOT.jar: 2 vulnerabilities (highest severity is: 9.9) reachable

[dev-mend-for-github-com]

Vulnerable Library - calcite-tutorial-common-1.0-SNAPSHOT.jar

Path to dependency file: /calcite-tutorial-9-rule/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (calcite-tutorial-common version)	Remediation Possible**	Reachability
CVE-2021-44228	Critical	9.9	log4j-core-2.13.2.jar	Transitive	N/A*	❌	Reachable
CVE-2021-45046	Critical	9.0	log4j-core-2.13.2.jar	Transitive	N/A*	❌	Unreachable

*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.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2021-44228

Vulnerable Library - log4j-core-2.13.2.jar

The Apache Log4j Implementation

Path to dependency file: /calcite-tutorial-common/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar

Dependency Hierarchy:

• calcite-tutorial-common-1.0-SNAPSHOT.jar (Root Library)
  • log4j-slf4j-impl-2.10.0.jar
    • ❌ log4j-core-2.13.2.jar (Vulnerable Library)

Found in base branch: master

Reachability Analysis

This vulnerability is potentially reachable

org.apache.logging.log4j.core.Logger (Application)
  -> org.apache.logging.slf4j.Log4jLogger (Extension)
   -> org.apache.logging.slf4j.Log4jLoggerFactory (Extension)
    -> org.apache.calcite.sql.validate.SqlValidatorException (Extension)
    ...
      -> org.apache.calcite.sql.validate.SqlValidatorUtil (Extension)
       -> org.apache.calcite.sql.SqlOperator (Extension)
        -> ❌ com.github.quxiucheng.calcite.parser.tutorial.SqlProperty (Vulnerable Component)

Vulnerability Details

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
Mend Note: Maria's test

Publish Date: 2021-12-10

URL: CVE-2021-44228

CVSS 3 Score Details (9.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • 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: GHSA-jfh8-c2jp-5v3q

Release Date: 2021-12-10

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

CVE-2021-45046

Vulnerable Library - log4j-core-2.13.2.jar

The Apache Log4j Implementation

Path to dependency file: /calcite-tutorial-common/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.2/log4j-core-2.13.2.jar

Dependency Hierarchy:

• calcite-tutorial-common-1.0-SNAPSHOT.jar (Root Library)
  • log4j-slf4j-impl-2.10.0.jar
    • ❌ log4j-core-2.13.2.jar (Vulnerable Library)

Found in base branch: master

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Publish Date: 2021-12-14

URL: CVE-2021-45046

CVSS 3 Score Details (9.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • 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://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-14

Fix Resolution: org.apache.logging.log4j:log4j-core:2.3.1,2.12.2,2.16.0;org.ops4j.pax.logging:pax-logging-log4j2:1.11.10,2.0.11