In Eclipse Jetty version 9.2.27, 9.3.26, and 9.4.16, the server running on Windows is vulnerable to exposure of the fully qualified Base Res
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.6% of all records.
- 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.
- Fixed version: org.eclipse.jetty:jetty-server (Maven) 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to org.eclipse.jetty:jetty-server (Maven) 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In Eclipse Jetty version 9.2.27, 9.3.26, and 9.4.16, the server running on Windows is vulnerable to exposure of the fully qualified Base Resource directory name on Windows to a remote client when it is configured for showing a Listing of directory contents. This information reveal is restricted to only the content in the configured base resource directories.
- Published
- Apr 22, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-213
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.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| eclipse | jetty | cpe:2.3:a:eclipse:jetty |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| netapp | oncommand system manager | cpe:2.3:a:netapp:oncommand_system_manager |
| netapp | snap creator framework | cpe:2.3:a:netapp:snap_creator_framework |
| netapp | snapcenter | cpe:2.3:a:netapp:snapcenter |
| netapp | snapmanager | cpe:2.3:a:netapp:snapmanager |
| netapp | storage replication adapter for clustered data ontap | cpe:2.3:a:netapp:storage_replication_adapter_for_clustered_data_ontap |
| netapp | storage services connector | cpe:2.3:a:netapp:storage_services_connector |
| netapp | vasa provider for clustered data ontap | cpe:2.3:a:netapp:vasa_provider_for_clustered_data_ontap |
| netapp | virtual storage console | cpe:2.3:a:netapp:virtual_storage_console |
| netapp | element | cpe:2.3:o:netapp:element |
| oracle | autovue | cpe:2.3:a:oracle:autovue |
and 14 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- eclipse jetty9.2.27
- eclipse jetty9.3.26
- eclipse jetty9.4.16
- netapp elementall versions
- netapp oncommand system manager3.0 and later · up to 3.1.3 inclusive
- netapp snap creator frameworkall versions
- netapp snapcenterall versions
- netapp snapmanagerall versions
- netapp storage replication adapter for clustered data ontap9.6 and later
- netapp storage replication adapter for clustered data ontap9.6
- netapp storage services connectorall versions
- netapp vasa provider for clustered data ontap9.6 and later
- netapp vasa provider for clustered data ontapall versions
- netapp virtual storage console9.6 and later
- netapp virtual storage console9.6
- oracle autovue21.0.2
- oracle communications analytics12.1.1
- oracle communications element manager8.0.0
- oracle communications element manager8.1.0
- oracle communications element manager8.1.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
- 9.2.27, 9.3.26, 9.4.16affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.eclipse.jetty:jetty-server | from 9.2.0 · before 9.2.28.v20190418 | 9.2.28.v20190418 |
| Maven | org.eclipse.jetty:jetty-server | from 9.3.0 · before 9.3.27.v20190418 | 9.3.27.v20190418 |
| Maven | org.eclipse.jetty:jetty-server | from 9.4.0 · before 9.4.17.v20190418 | 9.4.17.v20190418 |
Same product
eclipse: all recordsOther highest-scoring records for the same primary product.
- 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 con60This week
- 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 segm60This week
- CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem53Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-12545Mar 27, 2019 · In Eclipse Jetty version 9.3.x and 9.4.x, the server is vulnerable to Denial of Service conditions if a remote client sends either large SET32Monitor
- ← EarlierCVE-2019-10241Apr 22, 2019 · In Eclipse Jetty version 9.2.26 and older, 9.3.25 and older, and 9.4.15 and older, the server is vulnerable to XSS conditions if a remote cl27Monitor
- Later →CVE-2019-10247Apr 22, 2019 · In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version 23Monitor
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 |
|---|---|---|
| Maven:org.eclipse.jetty:jetty-server | 9.2.28.v20190418 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-server | 9.3.27.v20190418 | Package registry (OSV) |
| Maven:org.eclipse.jetty:jetty-server | 9.4.17.v20190418 | 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ı)
- TR-21-0331 · Apr 21, 2021(Oracle Güvenlik Uyarısı 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-213 · Exposure of Sensitive Information Due to Incompatible PoliciesCVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3%40%3Ccommits.nifi.apache.org%3E
- lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b%40%3Ccommits.nifi.apache.org%3E
- security.netapp.com/advisory/ntap-20190509-0003/
- www.oracle.com/security-alerts/cpuApr2021.html
- www.oracle.com/security-alerts/cpuapr2020.html
- www.oracle.com/security-alerts/cpujan2020.html
- www.oracle.com/security-alerts/cpujan2021.html
- www.oracle.com/security-alerts/cpujul2020.html
- 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.