Skip to main content
Public proof of conceptFix available

CVE-2023-40167

A public proof of concept exists; no exploitation attested.

  • Published2023-09-15
  • Fixed in12.0.1 · 11.0.16 · 10.0.16 · 9.4.52
  • WeaknessCWE-130

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-09-1520:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Versions per branch

OSV · NVD
Eclipse jetty
BranchAffectedFixed in
12.0≥ 12.0.0, < 12.0.112.0.1
11.0≥ 11.0.0, < 11.0.1611.0.16
10.0≥ 10.0.0, < 10.0.1610.0.16
9.x≥ 9.0.0, < 9.4.529.4.52
12.0= 12.0.0no fix published
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published
11.0= 11.0no fix published
12.0= 12.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • eclipse jetty.project
    Affected
    • = >= 9.0.0, <= 9.4.51no fix stated
    • = >= 10.0.0, <= 10.0.15no fix stated
    • = >= 11.0.0, <= 11.0.15no fix stated
    • = = 12.0.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-09-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-druidMinimOSall versions · fixed in 38.0.0-r0and 1 other package
  • apache-hiveCleanStartall versions · fixed in 3.1.3-r3
  • apache-hiveCleanStartall versions · fixed in 4.0.0-r1
  • candlepinRed Hat:satellite:6.14::el8all versions · fixed in 0:4.3.11-1.el8satand 1 other package
  • cassandra-reaperWolfiall versions · fixed in 4.0.1-r1
  • cassandra-reaperChainguardall versions · fixed in 4.0.1-r1
  • cloudwatch-exporterWolfiall versions · fixed in 0.15.4-r3
  • cloudwatch-exporterChainguardall versions · fixed in 0.15.4-r3

71 more package ranges on OSV.dev

Vendor advisories

  • RHSA-2024:3354 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Fuse 7.13.0 release and security update

  • RHSA-2024:2010 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Satellite 6.15.0 release

  • RHSA-2024:0797 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Satellite 6.14.2 Async Security Update

  • RHSA-2024:0778 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Jenkins and Jenkins-2-plugins security update

  • RHSA-2023:7697 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: AMQ Clients 2023.Q4

  • RHSA-2023:7678 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat AMQ Streams 2.6.0 release and security update

3 more advisories

Full record on NVD

Fix

  1. Update Eclipse jetty to 12.0.1 · 11.0.16 · 10.0.16 · 9.4.52
  2. Vendor fix Red Hat Product Security RHSA-2024:3354 · 1 productBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2024:2010 · 4 productsFor details on how to apply this update, refer to: * For upgrading connected Satellite: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.15/html-single/upgrading_connected_red_hat_satellite_to_6.15 * For upgrading disconnected Satellite: https://access.redhat.com/documentation/en-u…
  4. Vendor fix Red Hat Product Security RHSA-2024:0778 · 2 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  5. Vendor fix Red Hat Product Security RHSA-2023:7678 · 1 productBefore applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. The References section of this erratum contains a download link (you must log in to download the update).

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Published
2023-09-15
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-hmr7-m48g-48f6

Frequently asked questions

What is CVE-2023-40167?

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.

Is CVE-2023-40167 actively exploited?

Active exploitation of CVE-2023-40167 has not been confirmed. Its EPSS score was 1.3% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-40167?

CVE-2023-40167 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.

Running Satellite 6.14.2 Async? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record