# CVE-2005-3164: Apache Tomcat AJP Connector Information Leak

> An attacker can leak sensitive request body data from previous requests by exploiting improper handling of broken connections in the AJP connector.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qhqv-q4xg-f6g7

## What is CVE-2005-3164?

CVE-2005-3164 is a low-severity vulnerability in Apache Tomcat, published on 6 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AJP connector in Apache Tomcat 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standalone, does not properly handle when a connection is broken before request body data is sent in a POST request, which can lead to an information leak when "unsuitable request body data" is used for a different request, possibly related to Java Servlet pages.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2005-3164?

4 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | From 4.0.1 to 4.0.6 | None |
| `org.apache.tomcat:tomcat` | Maven | From 4.0.1 to 4.0.6 | None |
| `org.apache.tomcat:tomcat` | Maven | From 4.1.0 to 4.1.36 | None |
| `org.apache.tomcat:tomcat` | Maven | From 4.1.0 to 4.1.36 | None |

Products: Apache Tomcat, Hitachi Cosminexus Application Server.

## How do I fix CVE-2005-3164?

No fix has been published for CVE-2005-3164 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-3164 being exploited?

There is no known exploitation of CVE-2005-3164 in the wild and no public exploit code.

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3164 and fix it if it is affected.

What it is: CVE-2005-3164 is a low-severity vulnerability in Apache Tomcat, published on 6 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3164 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected from 4.0.1 up to 4.0.6; no fix listed
- org.apache.tomcat:tomcat (Maven): affected from 4.0.1 up to 4.0.6; no fix listed
- org.apache.tomcat:tomcat (Maven): affected from 4.1.0 up to 4.1.36; no fix listed
- org.apache.tomcat:tomcat (Maven): affected from 4.1.0 up to 4.1.36; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-3164/ (Markdown: https://insights.sbomify.com/CVE-2005-3164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-3164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-3164
- OSV: https://osv.dev/vulnerability/CVE-2005-3164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-3164/
Summaries are generated and may contain mistakes; the official description above is the record.