CVE-2009-1524 json
Cross-site scripting (XSS) vulnerability in Mort Bay Jetty before 6.1.17 allows remote attackers to inject arbitrary web script or HTML via…
published 2009-05-05 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1520
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in Mort Bay Jetty before 6.1.17 allows remote attackers to inject arbitrary web script or HTML via a directory listing request containing a ; (semicolon) character.
Patch / fix
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-1524 updated
: multiple vulnerabilities in jetty
-
Red Hat All currently supported Red Hat productsnot 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
Exploit prediction
2.59% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
jira.codehaus.org
/browse/JETTY-980
patch
-
itrc.hp.com
/service/cki/docDisplay.do?docId=emr_na-c02282388
vendor-advisory
-
secunia.com
/advisories/34975
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/34800
vdb-entry
-
vupen.com
/english/advisories/2010/1792
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=499867
-
secunia.com
/advisories/40553
third-party-advisory
Sources
- CVE List CVE-2009-1524
- NVD CVE-2009-1524
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.