Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-wph7-x527-w3h5

HIGH

Missing Release of Resource after Effective Lifetime in Apache Tomcat

Also known asBIT-tomcat-2021-42340CVE-2021-42340
Published
Oct 15, 2021
Updated
Mar 11, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
11.0%probability of exploitation in next 30 days
Moderate Risk95th percentile+6.71%
0.00%4.54%9.08%13.6%2.3%11.0%Dec 25Apr 26Jun 26

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.

Blast Radius

4 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.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 fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak. The object introduced to collect metrics for HTTP upgrade connections was not released for WebSocket connections once the connection was closed. This created a memory leak that, over time, could lead to a denial of service via an OutOfMemoryError.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat10.1.0-M1&&< 10.1.0-M610.1.0-M6
Mavenorg.apache.tomcat:tomcat10.0.0-M1&&< 10.0.1210.0.12
Mavenorg.apache.tomcat:tomcat9.0.40&&< 9.0.549.0.54
Mavenorg.apache.tomcat:tomcat8.5.60&&< 8.5.728.5.72

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.1.0-M6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wph7-x527-w3h5 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 pinpoints whether GHSA-wph7-x527-w3h5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wph7-x527-w3h5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak. The object introduced to collect metrics for HTTP upgrade connections was not released for WebSocket connections once the connection was closed. This created a memory leak that, over time, could lead to a denial of service via an OutOfMemoryError.
O3 Security · Impact-Aware SCA

Is GHSA-wph7-x527-w3h5 in your dependencies?

O3 detects GHSA-wph7-x527-w3h5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.