# Information Exposure vulnerability in Eclipse Jetty

Advisory record · `GHSA-r28m-g6j9-r2h5`

- **Identifiers:** `GHSA-r28m-g6j9-r2h5` · `CVE-2019-10246`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-213](https://cwe.mitre.org/data/definitions/213.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-213](https://agentprime.io/advisories/tag/cwe-213.md)
- **Published:** 23 Apr 2019
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Apr 2019, 16:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.eclipse.jetty:jetty-server` (Maven): affected `>=9.2.0, <9.2.28.v20190418 || >=9.3.0, <9.3.27.v20190418 || >=9.4.0, <9.4.17.v20190418`; fixed in `9.2.28.v20190418`, `9.3.27.v20190418`, `9.4.17.v20190418`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.041, the 90th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 23 Apr 2019. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-r28m-g6j9-r2h5](https://github.com/advisories/GHSA-r28m-g6j9-r2h5)
- [OSV: GHSA-r28m-g6j9-r2h5](https://osv.dev/vulnerability/GHSA-r28m-g6j9-r2h5)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-10246>
- <https://bugs.eclipse.org/bugs/show_bug.cgi?id=546576>
- <https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E>
- <https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E>
- <https://security.netapp.com/advisory/ntap-20190509-0003>
- <https://www.oracle.com/security-alerts/cpuApr2021.html>
- <https://www.oracle.com/security-alerts/cpuapr2020.html>
- <https://www.oracle.com/security-alerts/cpujan2020.html>
- <https://www.oracle.com/security-alerts/cpujan2021.html>
- <https://www.oracle.com/security-alerts/cpujul2020.html>
- <https://www.oracle.com/security-alerts/cpuoct2020.html>
- <https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r28m-g6j9-r2h5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r28m-g6j9-r2h5/>. Everything for agents: <https://agentprime.io/llms.txt>.