CVE-2023-40167
Eclipse Jetty 9.0.0 – 9.4.52
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2023-40167 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Eclipse Jetty. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Jetty, an open-source Java web server and servlet container, is affected by a parsing inconsistency in its HTTP/1 handling prior to versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1. The server accepts a leading “+” character in the Content-Length header value, which deviates from RFC 9110 requirements and from the stricter behavior of many other HTTP implementations that respond with a 400 status.
An unauthenticated network attacker could send such a malformed request in an attempt to trigger request-smuggling conditions when Jetty is placed behind or in front of another server that fails to close the connection after issuing a 400 response. Although no concrete exploit scenario has been identified, the permissive parsing could allow an attacker to manipulate request framing and potentially reach protected resources or bypass access controls in certain proxy or load-balanced deployments.
The project’s security advisory and downstream distributions such as Debian advise immediate upgrade to the patched releases; no configuration workaround exists. Public references, including the GitHub advisory GHSA-hmr7-m48g-48f6 and the associated RFC section, document the discrepancy and the fix.
EPSS scores have remained low, with a current value of 0.0457 and a peak of only 0.0553, indicating limited observed exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2523
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.5V4.2.1V4.2.2
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce length validation and input sanitization during coding and review.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect length-inconsistency vulnerabilities before deployment.
Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.
Application security requirements include explicit rules for handling message lengths and data structures.
Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.
Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.