Community
Participate
Working Groups
For Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, if an exception is thrown from the SessionListener#sessionDestroyed() method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in. CWEs CWE-613 CVSS Score 2.9 Low CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N Workarounds The application should catch all Throwables within their SessionListener#sessionDestroyed() implementations. This is currently fixed in Jetty 9.4.41, 10.0.3, and 11.0.3.
Do you have a security advisory, issue, or pull request that we can reference for more information?
Found it. https://github.com/eclipse/jetty.project/security/advisories/GHSA-m6cp-vxjx-65j6#advisory-comment-66773