CVEvulnerability
CVE-2023-40167
5.3 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2023-09-15
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CVSS 3.1 ([email protected])
- 5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-130
Description
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.
Affected configurations
• eclipse jetty (>= 9.0.0 < 9.4.52)
• eclipse jetty (>= 10.0.0 < 10.0.16)
• eclipse jetty (>= 11.0.0 < 11.0.16)
• eclipse jetty 12.0.0
• debian debian linux 10.0
• debian debian linux 11.0
• debian debian linux 12.0
Related
Weakness · CWE (1)
- CWE-130 Improper Handling of Length Parameter Inconsistency weakness
References
- https://github.com/eclipse/jetty.project/security/advisories/GHSA-hmr7-m48g-48f6 Vendor Advisory
- https://lists.debian.org/debian-lts-announce/2023/09/msg00039.html Mailing List, Third Party Advisory
- https://www.debian.org/security/2023/dsa-5507 Third Party Advisory
- https://www.rfc-editor.org/rfc/rfc9110#section-8.6 Technical Description
- https://github.com/eclipse/jetty.project/security/advisories/GHSA-hmr7-m48g-48f6 Vendor Advisory
- https://lists.debian.org/debian-lts-announce/2023/09/msg00039.html Mailing List, Third Party Advisory
- https://www.debian.org/security/2023/dsa-5507 Third Party Advisory
- https://www.rfc-editor.org/rfc/rfc9110#section-8.6 Technical Description