Skip to content
Fencer Vulns
medium 5.3

CVE-2009-1523 json

Directory traversal in Mort Bay Jetty

published 2009-05-05 17 y ago modified 2026-09-10 1 mo ago also GHSA-9986-w5h5-vw59 , EUVD-2022-3335

cvss
5.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
25.8%
EPSS 25.8% chance of exploitation in 30 days, percentile 97%
public exploits
2
Exploit-DB

Summary

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.

Patch / fix

  • maven org.mortbay.jetty:jetty 6.1.17, 7.0.0.M2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-1523 updated

: multiple vulnerabilities in jetty

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-36318)

Exploit prediction

25.80% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-36318 Jetty Web Server - Directory Traversal remote, 2011-11-18
  • EDB-18138 VMware - Update Manager Directory Traversal remote, 2011-11-21

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.mortbay.jetty:jetty
<6.1.17
>=7.0.0.M0, <7.0.0.M2
6.1.17
7.0.0.M2

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.