First published: Mon Oct 14 2024(Updated: )
### 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
Credit: emo@eclipse.org emo@eclipse.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.eclipse.jetty:jetty-servlets | >=12.0.0<=12.0.3 | 12.0.4 |
maven/org.eclipse.jetty:jetty-servlets | >=11.0.0<=11.0.17 | 11.0.18 |
maven/org.eclipse.jetty:jetty-servlets | >=10.0.0<=10.0.17 | 10.0.18 |
Eclipse Jetty | >=10.0.0<10.0.18 | |
Eclipse Jetty | >=11.0.0<11.0.18 | |
Eclipse Jetty | >=12.0.0<12.0.4 | |
>=10.0.0<10.0.18 | ||
>=11.0.0<11.0.18 | ||
>=12.0.0<12.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.