# CVE-2022-29885: EncryptInterceptor does not provide complete protection on insecure networks

> Apache Tomcat's EncryptInterceptor fails to prevent DoS attacks on untrusted networks, requiring configuration changes or patches to mitigate risks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2022
- **Updated:** 8 Oct 2026
- **Also known as:** BIT-tomcat-2022-29885, CLEANSTART-2026-OX03346, CLSA-2023-1689009963, CLSA-2023-1689010064, CLSA-2026-1777396783, DEBIAN-CVE-2022-29885, GHSA-r84p-88g2-2vx2, UBUNTU-CVE-2022-29885

## What is CVE-2022-29885?

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

### Official description

The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78 for the EncryptInterceptor incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was not correct. While the EncryptInterceptor does provide confidentiality and integrity protection, it does not protect against all risks associated with running over any untrusted network, particularly DoS risks.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-29885?

9 open source packages ship an affected version, including org.apache.tomcat:tomcat and tomcat. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | From 10.0.0-M1 | 10.0.21 |
| `org.apache.tomcat:tomcat` | Maven | From 10.0.0-M1 | 10.0.21 |
| `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.0-M15 |
| `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.0-M15 |
| `org.apache.tomcat:tomcat` | Maven | From 8.5.38 | 8.5.79 |
| `org.apache.tomcat:tomcat` | Maven | From 8.5.38 | 8.5.79 |
| `org.apache.tomcat:tomcat` | Maven | From 9.0.13 | 9.0.63 |
| `org.apache.tomcat:tomcat` | Maven | From 9.0.13 | 9.0.63 |
| `tomcat` | Bitnami | From 8.5.38 | 8.5.79, 9.0.63, 10.0.21 |

Products: Apache Tomcat, Debian Debian Linux, Oracle Hospitality Cruise Shipboard Property Management System.

## How do I fix CVE-2022-29885?

Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 10.0.21, 10.1.0-M15, 8.5.79 or 9.0.63.

## Is CVE-2022-29885 being exploited?

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

Public exploit code:

- Apache Tomcat CVE-2022-29885 (github_poc): https://github.com/quynhlab/CVE-2022-29885
- Apache Tomcat DoS (CVE-2022-29885) Exploit (github_poc): https://github.com/iveresk/CVE-2022-29885
- Apache Tomcat 10.1 - Denial Of Service (exploitdb)

## 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-2022-29885 and fix it if it is affected.

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

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected from 10.0.0-M1; fixed in 10.0.21
- org.apache.tomcat:tomcat (Maven): affected from 10.0.0-M1; fixed in 10.0.21
- org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.0-M15
- org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.0-M15
- org.apache.tomcat:tomcat (Maven): affected from 8.5.38; fixed in 8.5.79
- org.apache.tomcat:tomcat (Maven): affected from 8.5.38; fixed in 8.5.79
- org.apache.tomcat:tomcat (Maven): affected from 9.0.13; fixed in 9.0.63
- org.apache.tomcat:tomcat (Maven): affected from 9.0.13; fixed in 9.0.63
- tomcat (Bitnami): affected from 8.5.38; fixed in 8.5.79, 9.0.63, 10.0.21

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

## Sources

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

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