Use of Incorrectly-Resolved Name or Reference Affecting tomcat-servlet-4_0-api package, versions <9.0.36-4.58.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.29% (69th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES151-TOMCATSERVLET40API-2683242
  • published14 Apr 2022
  • disclosed1 Apr 2021

Introduced: 1 Apr 2021

CVE-2021-24122  (opens in a new tab)
CWE-706  (opens in a new tab)

How to fix?

Upgrade SLES:15.1 tomcat-servlet-4_0-api to version 9.0.36-4.58.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-servlet-4_0-api package and not the tomcat-servlet-4_0-api package as distributed by SLES. See How to fix? for SLES:15.1 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1