GitHub Advisoryadvisory · Maven

GHSA-wgmr-mf83-7x4j Jetty vulnerable to Invalid HTTP/2 requests that can lead to denial of service

HIGH Published 2022-07-07 Modified 2022-07-19 Official page ↗
Aliases
CVE-2022-2048
Ecosystem
Maven
Packages
org.eclipse.jetty.http2:http2-server
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400, CWE-410
Reviewed
2022-07-07

Affected packages

• Maven org.eclipse.jetty.http2:http2-server: < 9.4.47 → fixed in 9.4.47 • Maven org.eclipse.jetty.http2:http2-server: >= 10.0.0, < 10.0.10 → fixed in 10.0.10 • Maven org.eclipse.jetty.http2:http2-server: >= 11.0.0, < 11.0.10 → fixed in 11.0.10

Description

Description Invalid HTTP/2 requests (for example, invalid URIs) are incorrectly handled by writing a blocking error response directly from the selector thread. If the client manages to exhaust the HTTP/2 flow control window, or TCP congest the connection, the selector thread will be blocked trying to write the error response. If this is repeated for all the selector threads, the server becomes unresponsive, causing the denial of service. Impact A malicious client may render the server unresponsive. Patches The fix is available in Jetty versions 9.4.47. 10.0.10, 11.0.10. Workarounds No workaround available within Jetty itself. One possible workaround is to filter the requests before sending them to Jetty (for example in a proxy) For more information If you have any questions or comments about this advisory: • Email us at [email protected].

Related

Alias · CVE (1)

  • CVE-2022-2048 In Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up… vulnerability

Weakness · CWE (2)

  • CWE-400 Uncontrolled Resource Consumption weakness
  • CWE-410 Insufficient Resource Pool weakness

References