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

org.eclipse.jetty:jetty-http Updated 02 Oct 2025

Summary

07/07/2022
Yes i
Low
2.7

CVE-2022-2047: Jetty invalid URI parsing may produce invalid HttpURI.authority. Affects org.eclipse.jetty:jetty-http across 3 version ranges.

< 9.4.47 >= 10.0.0, < 10.0.10 >= 11.0.0, < 11.0.10

Fixed in 9.4.47, 10.0.10 or 11.0.10, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2022-2047 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The impacted package is org.eclipse.jetty:jetty-http, which is a part of the Jetty project. Jetty is a Java-based web server and servlet container that provides support for HTTP/2, WebSocket, and other Java web technologies. The jetty-http package specifically handles HTTP-related functionality. This vulnerability affects versions 9.4.0 and above, 10.0.0 and above, and 11.0.0 and above of the package.

Vulnerability Detail

The vulnerability in Jetty's HttpURI class allows for the parsing of invalid URIs, such as http://localhost;/path, as having an authority with a host of localhost;. This is incorrect behavior as the URI should either be considered invalid or interpret localhost; as the userinfo and no host. However, the HttpURI.host method returns localhost; instead of the expected result. This can lead to errors in Jetty's HttpClient and Jetty's ProxyServlet, AsyncProxyServlet, and AsyncMiddleManServlet, as they may wrongly interpret an authority with no host as one with a host. The impact of this vulnerability can result in unexpected behavior, incorrect routing, or security issues.

How To Fix

Latest published version: 12.1.14 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 9.4.47 9.4.47
  • >= 10.0.0, < 10.0.10 10.0.10
  • >= 11.0.0, < 11.0.10 11.0.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There are no known workarounds for this vulnerability.

Conclusion

The vulnerability in Jetty's HttpURI class can lead to errors and unexpected behavior in Jetty's HttpClient and ProxyServlet, AsyncProxyServlet, and AsyncMiddleManServlet. It is recommended to update the org.eclipse.jetty:jetty-http package to the patched versions (9.4.47, 10.0.10, or 11.0.10) to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for org.eclipse.jetty:jetty-http →

Share this vulnerability

FAQ

The impact of this vulnerability can result in errors with Jetty's HttpClient and Jetty's ProxyServlet, AsyncProxyServlet, and AsyncMiddleManServlet. It can lead to unexpected behavior, incorrect routing, or security issues.

Versions 9.4.0 and above, 10.0.0 and above, and 11.0.0 and above of the org.eclipse.jetty:jetty-http package are affected.

To fix this vulnerability, update the org.eclipse.jetty:jetty-http package to version 9.4.47 if using Jetty 9.4.x, or version 10.0.10 or 11.0.10 if using Jetty 10.x or 11.x.

There are no known workarounds for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for org.eclipse.jetty:jetty-http.

How To Fix

Latest published version: 12.1.14 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 9.4.47 9.4.47
  • >= 10.0.0, < 10.0.10 10.0.10
  • >= 11.0.0, < 11.0.10 11.0.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback