# CVE-2014-0095: Denial of service in Apache Tomcat

> Remote attackers can cause a denial of service in Apache Tomcat by sending AJP requests with zero content length, leading to thread exhaustion.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wf5v-jhxj-q632

## What is CVE-2014-0095?

CVE-2014-0095 is a medium-severity denial of service vulnerability in Apache Tomcat, published on 31 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

java/org/apache/coyote/ajp/AbstractAjpProcessor.java in Apache Tomcat 8.x before 8.0.4 allows remote attackers to cause a denial of service (thread consumption) by using a "Content-Length: 0" AJP request to trigger a hang in request processing.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-0095?

4 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core and org.apache.tomcat:tomcat-coyote. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0-RC1 | 8.0.4 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0-RC1 | 8.0.4 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 8.0.0-RC1 | 8.0.4 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 8.0.0-RC1 | 8.0.4 |

Products: Apache Tomcat.

## How do I fix CVE-2014-0095?

Upgrade org.apache.tomcat.embed:tomcat-embed-core to 8.0.4 or later.

## Is CVE-2014-0095 being exploited?

There is no known exploitation of CVE-2014-0095 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-2014-0095 and fix it if it is affected.

What it is: CVE-2014-0095 is a medium-severity denial of service vulnerability in Apache Tomcat, published on 31 May 2014. 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-2014-0095 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0-RC1; fixed in 8.0.4
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0-RC1; fixed in 8.0.4
- org.apache.tomcat:tomcat-coyote (Maven): affected from 8.0.0-RC1; fixed in 8.0.4
- org.apache.tomcat:tomcat-coyote (Maven): affected from 8.0.0-RC1; fixed in 8.0.4

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-2014-0095/ (Markdown: https://insights.sbomify.com/CVE-2014-0095/index.md)
```

## Sources

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

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