In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that do
In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.
- Published
- Jun 27, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- CWE-209
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.4%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| eclipse | jetty | cpe:2.3:a:eclipse:jetty |
| oracle | retail xstore point of service | cpe:2.3:a:oracle:retail_xstore_point_of_service |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- eclipse jetty9.3.0 and later · before 9.3.24
- eclipse jetty9.4.0 and later · before 9.4.11
- eclipse jetty9.0.0 and later · up to 9.2.26 inclusive
- oracle retail xstore point of service15.0
- oracle retail xstore point of service16.0.0
- oracle retail xstore point of service17.0
- oracle retail xstore point of service7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.
The Eclipse Foundation Eclipse Jetty
- unspecified and later · up to and including 9.2.0affected
- 9.3.0 and later · before unspecifiedaffected
- unspecified and later · before 9.3.24affected
- 9.4.0 and later · before unspecifiedaffected
- unspecified and later · before 9.4.11affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | jetty9 | before 9.2.25-1 | 9.2.25-1 |
| Debian:9 | jetty9 | before 9.2.30-0+deb9u1 | 9.2.30-0+deb9u1 |
| Maven | org.eclipse.jetty:jetty-server | from 9.0.0 · before 9.3.24.v20180605 | 9.3.24.v20180605 |
| Maven | org.eclipse.jetty:jetty-server | from 9.4.0 · before 9.4.11.v20180605 | 9.4.11.v20180605 |
Same product
eclipse: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem53Plan
- CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con51Plan
- CVE-2021-28165In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large inva46Plan
- CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm46Plan
- CVE-2021-28169For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to a45Plan
- CVE-2017-7658In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when pr45Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:jetty9 | 9.2.25-1 · Debian:12 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-server | 9.3.24.v20180605 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-server | 9.4.11.v20180605 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0533 · Jun 30, 2021(IBM Güvenlik Bülteni Yayınladı)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-209 · Generation of Error Message Containing Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securitytracker.com/id/1041194
- bugs.eclipse.org/bugs/show_bug.cgi?id=535670
- lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272%40%3Cissues.activemq.apache.org%3E
- lists.debian.org/debian-lts-announce/2021/05/msg00016.html
- security.netapp.com/advisory/ntap-20181014-0001/
- support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbst03953en_us
- www.oracle.com/security-alerts/cpuoct2020.html
- www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.