cve.bz

CVE-2024-7708 eclipse jetty: Uncontrolled Resource Consumption

7.5 highEPSS 0.4%Fix available

High (7.5) in eclipse jetty. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.eclipse.jetty:jetty-server 10.0.23, 11.0.23.

On this page
For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow can leak.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-7708 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-7708?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-7708?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-7708 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Jettyfrom 10.0.7 before 10.0.23
Eclipse Foundation Eclipse Jettyfrom 11.0.7 before 11.0.23

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9299-c6m4-mjhcMavenorg.eclipse.jetty:jetty-server>=10.0.7 <10.0.2310.0.23
GHSA-9299-c6m4-mjhcMavenorg.eclipse.jetty:jetty-server>=11.0.7 <11.0.2311.0.23

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12jetty9no fix listedDEBIAN-CVE-2024-7708
Debian13, 14jetty9, jetty12no fix listedDEBIAN-CVE-2024-7708
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 2 morejetty9no fix listedUBUNTU-CVE-2024-7708
Ubuntu26.04:LTS, 26.10jetty9, jetty12no fix listedUBUNTU-CVE-2024-7708

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat's version of Eclipse Jetty (9.0.3) shipped in Red Hat Enterprise Linux 7 is not affected by this vulnerability. The flaw was introduced in Jetty 10.0.0 and affects versions 10.0.0 through 10.0.22 and 11.0.0 through 11.0.22. The shipped version predates the introduction of the vulnerable code.

Red Hat's mitigation

No mitigation is needed as Red Hat products are not affected by this vulnerability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 7jettyNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-7708.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON