CVE-2019-17632
MEDIUMCVE-2019-17632 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.eclipse.jetty:jetty-server. O3 Security confirms whether CVE-2019-17632 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Unescaped exception messages in error responses in Jetty
Real-World Exposure
org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-serverReal-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
In Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and 9.4.23.v20191118, the generation of default unhandled Error response content (in text/html and text/json Content-Type) does not escape Exception messages in stacktraces included in error output.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty:jetty-server | ≥ 9.4.21.v20190926&&< 9.4.24.v20191120 | 9.4.24.v20191120 |
| ☕Maven | org.eclipse.jetty:jetty-server | ≥ 9.4.22.v20191022&&< 9.4.24.v20191120 | 9.4.24.v20191120 |
| ☕Maven | org.eclipse.jetty:jetty-server | ≥ 9.4.23.v20191118&&< 9.4.24.v20191120 | 9.4.24.v20191120 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server. 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.eclipse.jetty:jetty-server to 9.4.24.v20191120 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17632 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 CVE-2019-17632 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 CVE-2019-17632. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-17632 in your dependencies?
O3 detects CVE-2019-17632 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.