# Jetty vulnerable to exposure of sensitive information to unauthenticated remote users

Advisory record · `GHSA-ghgj-3xqr-6jfm`

- **Identifiers:** `GHSA-ghgj-3xqr-6jfm` · `CVE-2015-2080`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 9 Nov 2018
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Nov 2018, 17:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.75 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.eclipse.jetty:jetty-server` (Maven): affected `<9.2.9.v20150224`; fixed in `9.2.9.v20150224`

## 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

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.75, the 99th percentile, on 19 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 9 Nov 2018. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-ghgj-3xqr-6jfm](https://github.com/advisories/GHSA-ghgj-3xqr-6jfm)
- [OSV: GHSA-ghgj-3xqr-6jfm](https://osv.dev/vulnerability/GHSA-ghgj-3xqr-6jfm)
- <https://nvd.nist.gov/vuln/detail/CVE-2015-2080>
- <https://blog.gdssecurity.com/labs/2015/2/25/jetleak-vulnerability-remote-leakage-of-shared-buffers-in-je.html>
- <https://github.com/advisories/GHSA-ghgj-3xqr-6jfm>
- <https://github.com/eclipse/jetty.project/blob/jetty-9.2.x/advisories/2015-02-24-httpparser-error-buffer-bleed.md>
- <https://security.netapp.com/advisory/ntap-20190307-0005>
- <http://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00074.html>
- <http://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00075.html>
- <http://lists.fedoraproject.org/pipermail/package-announce/2015-March/151804.html>
- <http://packetstormsecurity.com/files/130567/Jetty-9.2.8-Shared-Buffer-Leakage.html>
- <http://seclists.org/fulldisclosure/2015/Mar/12>
- <http://www.securityfocus.com/archive/1/534755/100/1600/threaded>
- <http://www.securityfocus.com/bid/72768>

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-ghgj-3xqr-6jfm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ghgj-3xqr-6jfm/>. Everything for agents: <https://agentprime.io/llms.txt>.
