CVE-2021-24122 (Medium) detected in tomcat-embed-core-9.0.34.jar

[mend-for-github-com]

CVE-2021-24122 - Medium Severity Vulnerability

Vulnerable Library - tomcat-embed-core-9.0.34.jar

Core Tomcat implementation

Library home page: https://tomcat.apache.org/

Path to dependency file: /dd-smoke-tests/springboot-openliberty/application/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.34/tomcat-embed-core-9.0.34.jar

Dependency Hierarchy:

• spring-boot-starter-web-2.2.7.RELEASE.jar (Root Library)
  • spring-boot-starter-tomcat-2.2.7.RELEASE.jar
    • ❌ tomcat-embed-core-9.0.34.jar (Vulnerable Library)

Found in HEAD commit: 2819174635979a19573ec0ce8e3e2b63a3848079

Found in base branch: master

Vulnerability Details

When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.

Publish Date: 2021-01-14

URL: CVE-2021-24122

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122

Release Date: 2021-01-14

Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.40

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.2.12.RELEASE

---

• Check this box to open an automated fix PR

[mend-for-github-com]

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

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.