# CVE-2019-10246: Information Exposure vulnerability in Eclipse Jetty

> Remote attackers can view the fully qualified Base Resource directory name on Windows when directory listing is enabled in Eclipse Jetty.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** CLEANSTART-2026-FC70331, GHSA-r28m-g6j9-r2h5

## What is CVE-2019-10246?

CVE-2019-10246 is a medium-severity vulnerability in Eclipse Jetty, published on 22 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

## Which versions are affected by CVE-2019-10246?

6 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 25 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.2.0 | 9.2.28.v20190418 |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.2.0 | 9.2.28.v20190418 |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.3.0 | 9.3.27.v20190418 |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.3.0 | 9.3.27.v20190418 |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.4.0 | 9.4.17.v20190418 |
| `org.eclipse.jetty:jetty-server` | Maven | From 9.4.0 | 9.4.17.v20190418 |

Products: Eclipse Jetty, Netapp Element, Netapp Oncommand System Manager, Netapp Snap Creator Framework, Netapp Snapcenter, Netapp Snapmanager, Netapp Storage Replication Adapter for Clustered Data Ontap, Netapp Storage Services Connector, Netapp Vasa Provider for Clustered Data Ontap, Netapp Virtual Storage Console, Oracle Autovue, Oracle Communications Analytics, Oracle Communications Element Manager, Oracle Communications Services Gatekeeper, Oracle Communications Session Report Manager, Oracle Communications Session Route Manager, Oracle Data Integrator, Oracle Endeca Information Discovery Integrator, Oracle Enterprise Manager Base Platform, Oracle Flexcube Core Banking and 5 more.

## How do I fix CVE-2019-10246?

Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 9.2.28.v20190418, 9.3.27.v20190418 or 9.4.17.v20190418.

## Is CVE-2019-10246 being exploited?

There is no known exploitation of CVE-2019-10246 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Jetty

- [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8)
- [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4)
- [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8)
- [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7)
- [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10246 and fix it if it is affected.

What it is: CVE-2019-10246 is a medium-severity vulnerability in Eclipse Jetty, published on 22 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10246 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty:jetty-server (Maven): affected from 9.2.0; fixed in 9.2.28.v20190418
- org.eclipse.jetty:jetty-server (Maven): affected from 9.2.0; fixed in 9.2.28.v20190418
- org.eclipse.jetty:jetty-server (Maven): affected from 9.3.0; fixed in 9.3.27.v20190418
- org.eclipse.jetty:jetty-server (Maven): affected from 9.3.0; fixed in 9.3.27.v20190418
- org.eclipse.jetty:jetty-server (Maven): affected from 9.4.0; fixed in 9.4.17.v20190418
- org.eclipse.jetty:jetty-server (Maven): affected from 9.4.0; fixed in 9.4.17.v20190418

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10246/ (Markdown: https://insights.sbomify.com/CVE-2019-10246/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10246
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10246
- OSV: https://osv.dev/vulnerability/CVE-2019-10246

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10246/
Summaries are generated and may contain mistakes; the official description above is the record.