# CVE-2022-2047: Jetty invalid URI parsing may produce invalid HttpURI.authority

> Improper URI parsing in Jetty proxy mode can cause service failures, requiring an upgrade to stable versions.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** CLEANSTART-2025-XG26482, CLEANSTART-2026-AA47719, CLEANSTART-2026-SH51382, DEBIAN-CVE-2022-2047, ECHO-a71b-513c-424b, GHSA-cj7v-27pg-wf7q, MINI-6h68-826g-qjvc, MINI-p977-gv49-j35j, MINI-q527-w478-c7rq, UBUNTU-CVE-2022-2047

## What is CVE-2022-2047?

CVE-2022-2047 is a low-severity vulnerability in Debian Debian Linux, published on 7 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-2047?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty:jetty-http` | Maven | All versions | 9.4.47 |
| `org.eclipse.jetty:jetty-http` | Maven | All versions | 9.4.47 |
| `org.eclipse.jetty:jetty-http` | Maven | From 10.0.0 | 10.0.10 |
| `org.eclipse.jetty:jetty-http` | Maven | From 10.0.0 | 10.0.10 |
| `org.eclipse.jetty:jetty-http` | Maven | From 11.0.0 | 11.0.10 |
| `org.eclipse.jetty:jetty-http` | Maven | From 11.0.0 | 11.0.10 |

Products: Debian Debian Linux, Eclipse Jetty, Netapp Element Plug-in for Vcenter Server, Netapp Hci Compute Node, Netapp Management Services for Element Software and Netapp Hci, Netapp Snapcenter, Netapp Solidfire \& Hci Storage Node.

## How do I fix CVE-2022-2047?

Upgrade org.eclipse.jetty:jetty-http to a fixed version for your release line: 9.4.47, 10.0.10 or 11.0.10.

## Is CVE-2022-2047 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2047 and fix it if it is affected.

What it is: CVE-2022-2047 is a low-severity vulnerability in Debian Debian Linux, published on 7 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2047 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty:jetty-http (Maven): affected all versions; fixed in 9.4.47
- org.eclipse.jetty:jetty-http (Maven): affected all versions; fixed in 9.4.47
- org.eclipse.jetty:jetty-http (Maven): affected from 10.0.0; fixed in 10.0.10
- org.eclipse.jetty:jetty-http (Maven): affected from 10.0.0; fixed in 10.0.10
- org.eclipse.jetty:jetty-http (Maven): affected from 11.0.0; fixed in 11.0.10
- org.eclipse.jetty:jetty-http (Maven): affected from 11.0.0; fixed in 11.0.10

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-2022-2047/ (Markdown: https://insights.sbomify.com/CVE-2022-2047/index.md)
```

## Sources

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

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