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

GHSA-cx6h-86xw-9x34

HIGH

Apache Tomcat - Fix for CVE-2023-24998 was incomplete

Also known asBIT-tomcat-2023-28709CVE-2023-28709
Published
Jul 6, 2023
Updated
Mar 24, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
51.5%probability of exploitation in next 30 days
High Risk99th percentile+51.03%
0.00%22.3%44.7%67.0%0.1%51.5%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.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat:tomcat-coyote

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 CVE-2023-24998 was incomplete. If non-default HTTP connector settings were used such that the maxParameterCount could be reached using query string parameters and a request was submitted that supplied exactly maxParameterCount parameters in the query string, the limit for uploaded request parts could be bypassed with the potential for a denial of service to occur.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat.embed:tomcat-embed-core11.0.0-M2&&< 11.0.0-M511.0.0-M5
Mavenorg.apache.tomcat.embed:tomcat-embed-core10.1.5&&< 10.1.810.1.8
Mavenorg.apache.tomcat.embed:tomcat-embed-core9.0.71&&< 9.0.749.0.74
Mavenorg.apache.tomcat:tomcat-coyote8.5.85&&< 8.5.888.5.88

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.embed:tomcat-embed-core. 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.embed:tomcat-embed-core to 11.0.0-M5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cx6h-86xw-9x34 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-cx6h-86xw-9x34 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-cx6h-86xw-9x34. 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 CVE-2023-24998 was incomplete. If non-default HTTP connector settings were used such that the maxParameterCount could be reached using query string parameters and a request was submitted that supplied exactly maxParameterCount parameters in the query string, the limit for uploaded request parts could be bypassed with the potential for a denial of service to occur.
O3 Security · Impact-Aware SCA

Is GHSA-cx6h-86xw-9x34 in your dependencies?

O3 detects GHSA-cx6h-86xw-9x34 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.