CVE-2005-3164: Apache Tomcat AJP Connector Information Leak
Summary
CVE-2005-3164: Apache Tomcat AJP Connector Information Leak. Affects org.apache.tomcat:tomcat across 2 version ranges.
>= 4.0.1, <= 4.0.6
>= 4.1.0, <= 4.1.36
No fix is published. 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 widely used for hosting Java-based web applications. It provides a Java Servlet and JavaServer Pages (JSP) environment for running web applications. The AJP connector in Apache Tomcat versions 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standalone, is affected by an information leak vulnerability. This vulnerability occurs when a connection is broken before request body data is sent in a POST request. It can lead to an information leak when 'unsuitable request body data' is used for a different request, potentially exposing sensitive information from Java Servlet pages.
Vulnerability Detail
The vulnerability in the AJP connector of Apache Tomcat allows an attacker to obtain sensitive information by exploiting a flaw in the handling of broken connections during POST requests. When a connection is broken before request body data is sent, the AJP connector fails to properly handle this situation. As a result, if 'unsuitable request body data' is used for a subsequent request, it may leak information from Java Servlet pages. This information leak can potentially expose sensitive data, such as user credentials or other confidential information.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
If upgrading to a patched version is not immediately possible, a temporary workaround is to disable the AJP connector or restrict access to it. This can be done by modifying the server configuration to remove or comment out the AJP connector configuration. However, this workaround may impact the functionality of applications that rely on the AJP connector for communication.
Conclusion
The Apache Tomcat AJP Connector Information Leak vulnerability can potentially expose sensitive information from Java Servlet pages. It is recommended to upgrade to a patched version of Apache Tomcat (4.0.7 or 4.1.37 or later) to mitigate the risk. If immediate upgrade is not possible, disabling the AJP connector or restricting access to it can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.tomcat:tomcat →
FAQ
This vulnerability can lead to an information leak, potentially exposing sensitive data from Java Servlet pages. It could allow an attacker to obtain user credentials or other confidential information.
The vulnerability affects Apache Tomcat versions 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36.
There are no known public exploits for this vulnerability at the time of writing. However, it is still important to apply the necessary patches or upgrades to protect against potential attacks.
Yes, a fix for this vulnerability is available in Apache Tomcat versions 4.0.7 and 4.1.37 or later. Users are advised to update their Apache Tomcat installation to the latest version to mitigate the risk.
Yes, a temporary workaround is to disable the AJP connector or restrict access to it. However, this may impact the functionality of applications that rely on the AJP connector for communication.
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.tomcat:tomcat.
