Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-r84p-88g2-2vx2 — tomcat

HIGHFix: apache/tomcat@0fa7721

GHSA-r84p-88g2-2vx2 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.apache.tomcat:tomcat. 6 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Apache Tomcat EncryptInterceptor error leads to Uncontrolled Resource Consumption

Also known asBIT-tomcat-2022-29885CVE-2022-29885
Published
May 13, 2022
Updated
Mar 11, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
6 known
Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
73.5%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-r84p-88g2-2vx2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected
☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 10.1.0-M1&&< 10.1.0-M1510.1.0-M15org.apache.tomcat:tomcat:10.1.0-M15
☕Mavenorg.apache.tomcat:tomcat≥ 10.0.0-M1&&< 10.0.2110.0.21org.apache.tomcat:tomcat:10.0.21
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.13&&< 9.0.639.0.63org.apache.tomcat:tomcat:9.0.63
☕Mavenorg.apache.tomcat:tomcat≥ 8.5.38&&< 8.5.798.5.79org.apache.tomcat:tomcat:8.5.79
Exploits & PoCs
6

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51262dosmultiple

Apache Tomcat 10.1 - Denial Of Service

by Cristian Giustini · Apr 5, 2023

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.1.0-M15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r84p-88g2-2vx2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r84p-88g2-2vx2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r84p-88g2-2vx2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-r84p-88g2-2vx2 in your dependencies?

O3 Security finds GHSA-r84p-88g2-2vx2 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-r84p-88g2-2vx2: tomcat DoS (High 7.5) | O3 Security