CVE-2009-1523 — jetty
MEDIUMCVE-2009-1523 is a medium-severity (CVSS 5.3) Path Traversal vulnerability in org.mortbay.jetty:jetty. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.mortbay.jetty:jetty — see the affected versions and patch details below.
Directory traversal in Mort Bay Jetty
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.mortbay.jetty:jetty☕org.mortbay.jetty:jettyReal-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
Directory traversal vulnerability in the HTTP server in Mort Bay Jetty 5.1.14, 6.x before 6.1.17, and 7.x through 7.0.0.M2 allows remote attackers to access arbitrary files via directory traversal sequences in the URI.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.mortbay.jetty:jetty | all versions | 6.1.17org.mortbay.jetty:jetty:6.1.17 |
| ☕Maven | org.mortbay.jetty:jetty | ≥ 7.0.0.M0&&< 7.0.0.M2 | 7.0.0.M2org.mortbay.jetty:jetty:7.0.0.M2 |
Affected Products
jettymortbayResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Jetty Web Server - Directory Traversal
by Alexey Sintsov · Nov 18, 2011
VMware - Update Manager Directory Traversal
by Alexey Sintsov · Nov 21, 2011
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mortbay.jetty:jetty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mortbay.jetty:jetty to 6.1.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-1523 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2009-1523 in your dependencies?
Find it across Maven, including transitive dependencies.