CVE-2007-0450: Apache Tomcat Directory Traversal
Summary
CVE-2007-0450: Apache Tomcat Directory Traversal. Affects org.apache.tomcat:tomcat across 2 version ranges.
>= 5.0, < 5.5.22
>= 6.0, < 6.0.10
Fixed in 5.5.22 or 6.0.10, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Tomcat is an open-source web server and servlet container that is used to deploy Java-based web applications. It provides a Java Servlet and JavaServer Pages (JSP) environment for running web applications. The vulnerability in Apache Tomcat allows remote attackers to read arbitrary files through a directory traversal attack. This vulnerability affects versions 5.x before 5.5.22 and 6.x before 6.0.10 when certain proxy modules (mod_proxy, mod_rewrite, mod_jk) are used.
Vulnerability Detail
The vulnerability arises due to a directory traversal flaw in Tomcat. By exploiting this vulnerability, remote attackers can read arbitrary files on the server. The attack involves using a combination of .. (dot dot) sequences and certain characters like /, \, and URL-encoded backslash (%5C) in the URL. While these characters are valid separators in Tomcat, they are not recognized as such in Apache. This allows attackers to bypass file access restrictions and retrieve sensitive information from the server.
How To Fix
Latest published version: 11.0.27 as of 23 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 5.0, < 5.5.225.5.22 -
>= 6.0, < 6.0.106.0.10
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading to a fixed version is not immediately feasible, a temporary workaround is to disable the affected proxy modules (mod_proxy, mod_rewrite, mod_jk) in the Apache configuration. By disabling these modules, the vulnerability can be mitigated until a proper upgrade can be performed. Here is an example of how to disable the mod_proxy module in the Apache configuration:
# Disable mod_proxy
LoadModule proxy_module modules/mod_proxy.so
# Comment out the above line to disable the module
Please note that this workaround may impact the functionality of certain applications or services that rely on these modules.
Conclusion
The directory traversal vulnerability in Apache Tomcat can lead to unauthorized access to sensitive files on the server. It is crucial to apply the recommended fixes or workarounds to mitigate the risk of exploitation. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.tomcat:tomcat →
FAQ
The vulnerability allows remote attackers to read arbitrary files on the server, potentially exposing sensitive information such as configuration files, user data, or other confidential data.
Yes, this vulnerability can be exploited remotely by sending specially crafted requests to the affected server.
There have been reported instances of this vulnerability being exploited in the wild. It is important to apply the necessary patches or upgrades to protect against potential attacks.
The CVSS score for this vulnerability is not available in the provided information. It is recommended to refer to the National Vulnerability Database (NVD) or other reliable sources for the latest CVSS score.
Yes, a temporary workaround is to disable the affected proxy modules (mod_proxy, mod_rewrite, mod_jk) in the Apache configuration. However, it is strongly advised to upgrade to a fixed version as soon as possible.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.tomcat:tomcat.
