NetSight
mittel5.3

CVE-2023-40167

Jetty accepts "+" prefixed value in Content-Length

Auswirkung

### Impact 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. ### Workarounds There is no workaround as there is no known exploit scenario. ### Original Report [RFC 9110 Secion 8.6](https://www.rfc-editor.org/rfc/rfc9110#section-8.6) defined the value of Content-Length header should be a string of 0-9 digits. However we found that Jetty accepts "+" prefixed Content-Length, which could lead to potential HTTP request smuggling. Payload: ``` POST / HTTP/1.1 Host: a.com Content-Length: +16 Connection: close ​ 0123456789abcdef ``` When sending this payload to Jetty, it can successfully parse and identify the length. When sending this payload to NGINX, Apache HTTPd or other HTTP servers/parsers, they will return 400 bad request. This behavior can lead to HTTP request smuggling and can be leveraged to bypass WAF or IDS.

Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Bei Erfolg: geringes Risiko, dass Daten oder Systeme verändert werden.

Betroffene Pakete

ÖkosystemPaketBetroffenBehoben in
mavenorg.eclipse.jetty:jetty-http>= 9.0.0, <= 9.4.519.4.52

Betroffene Produkte

HerstellerProduktBetroffene Versionen
DebianDebian Linux
Versionen 10.0, 11.0, 12.0
EclipseJetty
ab 9.0.0 vor 9.4.52
ab 10.0.0 vor 10.0.16
ab 11.0.0 vor 11.0.16
Version 12.0.0

Schwachstellenklasse

Referenzen