Eclipse Jetty 12.0.0 Beta 2
Approved changes feed: RSS · Atom
cpe:2.3:a:eclipse:jetty:12.0.0:beta2:*:*:*:*:*:*
part: a version: 12.0.0 update: beta2
| Vendor | Eclipse (fa988180-604e-5c1f-93ea-65b5297000fc) |
|---|---|
| Product | Jetty (218f4e28-2142-514f-b269-fe7d12f8e0be) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:eclipse/jetty |
purl2cpe | 2026-06-01 10:15:03.376761 |
pkg:github/eclipse/jetty.project |
purl2cpe | 2026-06-01 10:15:03.376763 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-40167 |
vulnerable | 2026-06-03 14:52:42.651256 |
Jetty accepts "+" prefixed value in Content-Length
MEDIUM (5.3)
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.
Published: 2023-09-15T19:37:37.530Z
Updated: 2025-02-13T17:03:25.096Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.