Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-40167: Jetty accepts "+" prefixed value in Content-Length

Noroxi assessment

Priority: Monitor (action score 21/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 70% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: jetty9 (Debian:10) 9.4.16-0+deb10u3; jetty9 (Debian:11) 9.4.39-3+deb11u2; jetty9 (Debian:12) 9.4.50-4+deb12u1.

Low priority for now. Upgrade to jetty9 (Debian:10) 9.4.16-0+deb10u3; jetty9 (Debian:11) 9.4.39-3+deb11u2; jetty9 (Debian:12) 9.4.50-4+deb12u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—Proof of concept Fix available
Published
Sep 15, 2023
Updated
Jun 17, 2026
EPSS
1.2% · 70th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.3
CNA · GitHub_M
5.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-40167

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for eclipse records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
eclipsejetty
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux11.0
  • debian debian linux12.0
  • eclipse jetty10.0.0 and later · before 10.0.16
  • eclipse jetty11.0.0 and later · before 11.0.16
  • eclipse jetty9.0.0 and later · before 9.4.52
  • eclipse jetty12.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • eclipse jetty.project

    • >= 9.0.0, <= 9.4.51, >= 10.0.0, <= 10.0.15, >= 11.0.0, <= 11.0.15, = 12.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10jetty9before 9.4.16-0+deb10u39.4.16-0+deb10u3
Debian:11jetty9before 9.4.39-3+deb11u29.4.39-3+deb11u2
Debian:12jetty9before 9.4.50-4+deb12u19.4.50-4+deb12u1
Debian:13jetty9before 9.4.52-19.4.52-1
Mavenorg.eclipse.jetty:jetty-httpfrom 10.0.0 · before 10.0.1610.0.16
Mavenorg.eclipse.jetty:jetty-httpfrom 11.0.0 · before 11.0.1611.0.16
Mavenorg.eclipse.jetty:jetty-httpfrom 12.0.0 · before 12.0.112.0.1
Mavenorg.eclipse.jetty:jetty-httpfrom 9.0.0 · before 9.4.529.4.52
openSUSE:Leap 15.4jetty-minimalbefore 9.4.53-150200.3.22.19.4.53-150200.3.22.1
Red Hat:ocp_tools:4.12::el8jenkinsbefore 0:2.426.3.1706515686-3.el80:2.426.3.1706515686-3.el8
Red Hat:ocp_tools:4.12::el8jenkins-2-pluginsbefore 0:4.12.1706515741-1.el80:4.12.1706515741-1.el8
Red Hat:satellite_capsule:6.14::el8mosquittobefore 0:2.0.17-1.el8sat0:2.0.17-1.el8sat
Red Hat:satellite_capsule:6.14::el8mosquitto-debuginfobefore 0:2.0.17-1.el8sat0:2.0.17-1.el8sat
Red Hat:satellite_capsule:6.14::el8mosquitto-debugsourcebefore 0:2.0.17-1.el8sat0:2.0.17-1.el8sat
Red Hat:satellite_capsule:6.14::el8puppet-agentbefore 0:7.27.0-1.el8sat0:7.27.0-1.el8sat
Red Hat:satellite_capsule:6.14::el8puppetserverbefore 0:7.14.0-1.el8sat0:7.14.0-1.el8sat
Red Hat:satellite_capsule:6.15::el8foremanbefore 0:3.9.1.6-1.el8sat0:3.9.1.6-1.el8sat
Red Hat:satellite_capsule:6.15::el8foreman-debugbefore 0:3.9.1.6-1.el8sat0:3.9.1.6-1.el8sat
Red Hat:satellite_capsule:6.15::el8python-aiohttpbefore 0:3.9.2-1.el8pc0:3.9.2-1.el8pc
Red Hat:satellite_capsule:6.15::el8python-aiohttp-debugsourcebefore 0:3.9.2-1.el8pc0:3.9.2-1.el8pc
Red Hat:satellite_capsule:6.15::el8python-djangobefore 0:4.2.9-1.el8pc0:4.2.9-1.el8pc
Red Hat:satellite_capsule:6.15::el8python-galaxy-importerbefore 0:0.4.19-2.el8pc0:0.4.19-2.el8pc
Red Hat:satellite_capsule:6.15::el8python-jinja2before 0:3.1.3-1.el8pc0:3.1.3-1.el8pc
Red Hat:satellite_capsule:6.15::el8python-pycryptodomexbefore 0:3.20.0-1.el8pc0:3.20.0-1.el8pc

+36

Same product

eclipse: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con
    60This week
  • CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm
    60This week
  • CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem
    53Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-26049Apr 18, 2023 · Cookie parsing of quoted values can exfiltrate values from other cookies in Eclipse Jetty
    21Monitor
  • ← EarlierCVE-2023-36479Sep 15, 2023 · Jetty vulnerable to errant command quoting in CGI Servlet
    12Monitor
  • Later →CVE-2023-41900Sep 15, 2023 · Jetty's OpenId Revoked authentication allows one request
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:jetty99.4.50-4+deb12u1 · Debian:12Package registry (OSV)
Maven:org.eclipse.jetty:jetty-http10.0.16Package registry (OSV)
Maven:org.eclipse.jetty:jetty-http11.0.16Package registry (OSV)
Maven:org.eclipse.jetty:jetty-http12.0.1Package registry (OSV)
Maven:org.eclipse.jetty:jetty-http9.4.52Package registry (OSV)
opensuse:jetty-minimal9.4.53-150200.3.22.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:candlepin0:4.3.11-1.el8sat · Red Hat:satellite:6.14::el8Package registry (OSV)
red hat:candlepin-selinux0:4.3.11-1.el8sat · Red Hat:satellite:6.14::el8Package registry (OSV)
red hat:jenkins0:2.426.3.1706515686-3.el8 · Red Hat:ocp_tools:4.12::el8Package registry (OSV)
red hat:jenkins-2-plugins0:4.12.1706515741-1.el8 · Red Hat:ocp_tools:4.12::el8Package registry (OSV)
red hat:mosquitto0:2.0.17-1.el8sat · Red Hat:satellite_capsule:6.14::el8Package registry (OSV)
red hat:mosquitto-debuginfo0:2.0.17-1.el8sat · Red Hat:satellite_capsule:6.14::el8Package registry (OSV)
red hat:mosquitto-debugsource0:2.0.17-1.el8sat · Red Hat:satellite_capsule:6.14::el8Package registry (OSV)
red hat:puppet-agent0:7.27.0-1.el8sat · Red Hat:satellite_capsule:6.14::el8Package registry (OSV)
red hat:puppetserver0:7.14.0-1.el8sat · Red Hat:satellite_capsule:6.14::el8Package registry (OSV)
red hat:rubygem-grpc0:1.58.0-1.el8sat · Red Hat:satellite:6.14::el8Package registry (OSV)
red hat:rubygem-puma0:6.3.1-1.el8sat · Red Hat:satellite:6.14::el8Package registry (OSV)
red hat:rubygem-sidekiq0:6.5.12-1.el8sat · Red Hat:satellite:6.14::el8Package registry (OSV)
suse:jetty-minimal9.4.53-150200.3.22.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02025-03-03

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+534 d
  3. TodayNov 2, 2026+1143 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-130 · Improper Handling of Length Parameter Inconsistency

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records