Improper Handling of Length Parameter Inconsistency Affecting jetty-client package, versions <0:9.0.3-8.amzn2.0.3


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.1% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2-JETTYCLIENT-6253880
  • published20 Feb 2024
  • disclosed15 Sept 2023

Introduced: 15 Sep 2023

CVE-2023-40167  (opens in a new tab)
CWE-130  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 jetty-client to version 0:9.0.3-8.amzn2.0.3 or higher.
This issue was patched in ALAS2-2024-2460.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jetty-client package and not the jetty-client package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

Jetty is a Java based web server and servlet engine. Prior to versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1, Jetty accepts the + character proceeding the content-length value in a HTTP/1 header field. This is more permissive than allowed by the RFC and other servers routinely reject such requests with 400 responses. There is no known exploit scenario, but it is conceivable that request smuggling could result if jetty is used in combination with a server that does not close the connection after sending such a 400 response. Versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1 contain a patch for this issue. There is no workaround as there is no known exploit scenario.

CVSS Scores

version 3.1