CVE-2022-2047

Description

URI use within Jetty's HttpURI class can parse invalid URIs such as http://localhost;/path as having an authority with a host of localhost;.

A URIs of the type http://localhost;/path should be interpreted to be either invalid or as localhost; to be the userinfo and no host.
However, HttpURI.host returns localhost; which is definitely wrong.

Workarounds

None.

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected].

This can lead to errors with Jetty's HttpClient, and Jetty's ProxyServlet / AsyncProxyServlet / AsyncMiddleManServlet wrongly interpreting an authority with no host as one with a host.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-2047 has a CVSS score of 2.7 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.4.47, 10.0.10, 11.0.10); upgrading removes the vulnerable code path.

Kodem intelligence

Patched in PR #8146 for Jetty version 9.4.47.
Patched in PR #8014 for Jetty versions 10.0.10, and 11.0.10

1. What is CVE-2022-2047? CVE-2022-2047 is a low-severity improper input validation vulnerability in org.eclipse.jetty:jetty-http (maven), affecting versions < 9.4.47. It is fixed in 9.4.47, 10.0.10, 11.0.10. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-2047? CVE-2022-2047 has a CVSS score of 2.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.eclipse.jetty:jetty-http are affected by CVE-2022-2047? org.eclipse.jetty:jetty-http (maven) versions < 9.4.47 is affected.
4. Is there a fix for CVE-2022-2047? Yes. CVE-2022-2047 is fixed in 9.4.47, 10.0.10, 11.0.10. Upgrade to this version or later.
5. Is CVE-2022-2047 exploitable, and should I be worried? Whether CVE-2022-2047 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-2047 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-2047?
   • Upgrade org.eclipse.jetty:jetty-http to 9.4.47 or later
   • Upgrade org.eclipse.jetty:jetty-http to 10.0.10 or later
   • Upgrade org.eclipse.jetty:jetty-http to 11.0.10 or later