# CVE-2013-2071: Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

> Attackers can obtain sensitive request information intended for other applications via improper handling of RuntimeExceptions in async listeners.

- **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:** Yes
- **Published:** 1 Jun 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3p5r-7cw3-2m67, MGASA-2013-0191

## What is CVE-2013-2071?

CVE-2013-2071 is a low-severity vulnerability in Apache Tomcat, published on 1 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

java/org/apache/catalina/core/AsyncContextImpl.java in Apache Tomcat 7.x before 7.0.40 does not properly handle the throwing of a RuntimeException in an AsyncListener in an application, which allows context-dependent attackers to obtain sensitive request information intended for other applications in opportunistic circumstances via an application that records the requests that it processes.

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

## Which versions are affected by CVE-2013-2071?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.40 |
| `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.40 |

Products: Apache Tomcat.

## How do I fix CVE-2013-2071?

Upgrade org.apache.tomcat:tomcat to 7.0.40 or later.

## Is CVE-2013-2071 being exploited?

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

What it is: CVE-2013-2071 is a low-severity vulnerability in Apache Tomcat, published on 1 Jun 2013. 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-2013-2071 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.40
- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.40

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

## Sources

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

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