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

GHSA-3vx3-xf6q-r5xp

CRITICAL

Exposure of Resource to Wrong Sphere in Apache Tomcat

Also known asCVE-2017-5648
Published
May 13, 2022
Updated
Apr 18, 2024
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
12.7%probability of exploitation in next 30 days
Moderate Risk96th percentile-9.03%
0.00%8.98%18.0%26.9%4.5%12.7%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

8 pkgs affected
org.apache.tomcat:tomcat-catalinaorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat:tomcat-catalinaorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-coreorg.apache.tomcat.embed:tomcat-embed-core

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

While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat-catalina9.0.0.M1&&< 9.0.0.M189.0.0.M18
Mavenorg.apache.tomcat:tomcat-catalina8.5.0&&< 8.5.138.5.13
Mavenorg.apache.tomcat:tomcat-catalina8.0.0&&< 8.0.428.0.42
Mavenorg.apache.tomcat:tomcat-catalina7.0.0&&< 7.0.767.0.76
Mavenorg.apache.tomcat.embed:tomcat-embed-core9.0.0.M1&&< 9.0.0.M189.0.0.M18
Mavenorg.apache.tomcat.embed:tomcat-embed-core8.5.0&&< 8.5.138.5.13

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-catalina. 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-catalina to 9.0.0.M18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vx3-xf6q-r5xp 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-3vx3-xf6q-r5xp 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-3vx3-xf6q-r5xp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.
O3 Security · Impact-Aware SCA

Is GHSA-3vx3-xf6q-r5xp in your dependencies?

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