Directory Traversal Affecting log4j package, versions <0:1.2.12-1jpp_1rh


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
53.99% (98th 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 Learn

Learn about Directory Traversal vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL10-LOG4J-9875830
  • published28 Apr 2025
  • disclosed1 Jan 2008

Introduced: 1 Jan 2008

CVE-2008-5515  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade RHEL:10 log4j to version 0:1.2.12-1jpp_1rh or higher.
This issue was patched in RHSA-2010:0602.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j package and not the log4j package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalizes the target pathname before filtering the query string when using the RequestDispatcher method, which allows remote attackers to bypass intended access restrictions and conduct directory traversal attacks via .. (dot dot) sequences and the WEB-INF directory in a Request.

References

CVSS Base Scores

version 3.1