GHSA-f632-9449-3j4w
MEDIUMApache Tomcat - XSS in generated JSPs
EPSS Exploitation Probability
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
org.apache.tomcat:tomcat-jasper☕org.apache.tomcat:tomcat-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat:tomcat-jasper☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat+1 moreReal-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
Description:
The fix for improvement 69333 caused pooled JSP tags not to be released after use which in turn could cause output of some tags not to escaped as expected. This unescaped output could lead to XSS.
Versions Affected:
- Apache Tomcat 11.0.0
- Apache Tomcat 10.1.31
- Apache Tomcat 9.0.96
Mitigation:
Users of the affected versions should apply one of the following mitigations:
- Upgrade to Apache Tomcat 11.0.1 or later
- Upgrade to Apache Tomcat 10.1.33 or later Note: 10.1.32 was not released
- Upgrade to Apache Tomcat 9.0.97 or later
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 11.0.0&&< 11.0.1 | 11.0.1 |
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 10.1.31&&< 10.1.32 | 10.1.32 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 9.0.96&&< 9.0.97 | 9.0.97 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 11.0.0&&< 11.0.1 | 11.0.1 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 10.1.31&&< 10.1.32 | 10.1.32 |
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 9.0.96&&< 9.0.97 | 9.0.97 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-jasper. 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.
Fix
Update org.apache.tomcat:tomcat-jasper to 11.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f632-9449-3j4w is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-f632-9449-3j4w 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-f632-9449-3j4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f632-9449-3j4w in your dependencies?
O3 detects GHSA-f632-9449-3j4w across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.