# Jetty vulnerable to cache poisoning due to inconsistent HTTP request handling (HTTP Request Smuggling)

Advisory record · `GHSA-84q7-p226-4x5w`

- **Identifiers:** `GHSA-84q7-p226-4x5w` · `CVE-2017-7656`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-444](https://cwe.mitre.org/data/definitions/444.html)
- **Tags:** [HTTP request smuggling](https://agentprime.io/advisories/tag/request-smuggling.md)
- **Published:** 19 Oct 2018
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Oct 2018, 16:16 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.3.24.v20180605 || >=9.4.0, <9.4.11.v20180605`; fixed in `9.3.24.v20180605`, `9.4.11.v20180605`

## 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:N/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.061, the 93rd percentile, on 8 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 19 Oct 2018. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-84q7-p226-4x5w](https://github.com/advisories/GHSA-84q7-p226-4x5w)
- [OSV: GHSA-84q7-p226-4x5w](https://osv.dev/vulnerability/GHSA-84q7-p226-4x5w)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-7656>
- <https://bugs.eclipse.org/bugs/show_bug.cgi?id=535667>
- <https://github.com/advisories/GHSA-84q7-p226-4x5w>
- <https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@%3Cissues.activemq.apache.org%3E>
- <https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E>
- <https://lists.apache.org/thread.html/9317fd092b257a0815434b116a8af8daea6e920b6673f4fd5583d5fe@%3Ccommits.druid.apache.org%3E>
- <https://lists.apache.org/thread.html/rbf4565a0b63f9c8b07fab29352a97bbffe76ecafed8b8555c15b83c6@%3Cissues.maven.apache.org%3E>
- <https://security.netapp.com/advisory/ntap-20181014-0001>
- <https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbst03953en_us>
- <https://www.debian.org/security/2018/dsa-4278>
- <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-84q7-p226-4x5w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-84q7-p226-4x5w/>. Everything for agents: <https://agentprime.io/llms.txt>.