Skip to main content
VulnerabilityPublished Updated

CVE-2024-6762: Org.eclipse.jetty:jetty servlets: Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks

Affects org.eclipse.jetty:jetty-servletsSource GCVE Database

0
Compare
Authoritative record:CVE-2024-6762· Low 3.1

Not known to be exploited · CVSS 3.1 Low : upgrade to 10.0.18 when convenient.

Data as of 29 Oct 2026, 22:52 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 3.13.1
Patch
Available – fixed in 10.0.18, 11.0.18, 12.0.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade org.eclipse.jetty:jetty-servlets to 10.0.18; org.eclipse.jetty:jetty-servlets to 11.0.18; org.eclipse.jetty:jetty-servlets to 12.0.4.

Affected software

ProductAffectedFixed in
Mavenorg.eclipse.jetty:jetty-servletsAffected
  • >=10.0.0 <10.0.18
Fixed in
  • 10.0.18
Mavenorg.eclipse.jetty:jetty-servletsAffected
  • >=11.0.0 <11.0.18
Fixed in
  • 11.0.18
Mavenorg.eclipse.jetty:jetty-servletsAffected
  • >=12.0.0 <12.0.4
Fixed in
  • 12.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact Jetty PushSessionCacheFilter can be exploited by unauthenticated users to launch remote DoS attacks by exhausting the server’s memory. ### Patches * https://github.com/jetty/jetty.project/pull/9715 * https://github.com/jetty/jetty.project/pull/9716 ### Workarounds The session usage is intrinsic to the design of the PushCacheFilter. The issue can be avoided by: + not using the PushCacheFilter. Push has been deprecated by the various IETF specs and early hints responses should be used instead. + reducing the reducing the idle timeout on unauthenticated sessions will reduce the time such session stay in memory. + configuring a session cache to use [session passivation](https://jetty.org/docs/jetty/12/programming-guide/server/session.html), so that sessions are not stored in memory, but rather in a database or file system that may have significantly more capacity than memory. ### References * https://github.com/jetty/jetty.project/pull/10756 * https://github.com/jetty/jetty.project/pull/10755

References

Community reviews

Loading reviews…