jetty/jetty.project · Security
Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks
- GHSA ID
- GHSA-r7m4-f9h5-gr79
- CVE ID
- CVE-2024-6762
- Severity
- low
- Published
- Updated
- CVSS
- 3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
- CVSS v3
- 3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
- CVSS v4
- 2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Description
Impact
Jetty PushSessionCacheFilter can be exploited by unauthenticated users to launch remote DoS attacks by exhausting the server’s memory.
Patches
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, 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
CWEs
- CWE-400 · Uncontrolled Resource Consumption
- CWE-770 · Allocation of Resources Without Limits or Throttling
References
- https://github.com/jetty/jetty.project/security/advisories/GHSA-r7m4-f9h5-gr79 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2024-6762 ↗
- https://github.com/jetty/jetty.project/pull/10755 ↗
- https://github.com/jetty/jetty.project/pull/10756 ↗
- https://github.com/jetty/jetty.project/pull/9715 ↗
- https://github.com/jetty/jetty.project/pull/9716 ↗
- https://gitlab.eclipse.org/security/cve-assignement/-/issues/24 ↗
- https://lists.debian.org/debian-lts-announce/2025/04/msg00001.html ↗
- https://github.com/advisories/GHSA-r7m4-f9h5-gr79 ↗