LowGHSA-m6cp-vxjx-65j6CVE-2021-34428

SessionListener can prevent a session from being invalidated breaking logout

Published 23 Jun 2021 · Updated 8 Jul 2026

Is your project on an affected org.eclipse.jetty:jetty-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<9.4.41
Fixed in
9.4.41
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.4.41 -DforceVersion=true
Affected
>=10.0.0 <10.0.3
Fixed in
10.0.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=10.0.3 -DforceVersion=true
Affected
>=11.0.0 <11.0.3
Fixed in
11.0.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=11.0.3 -DforceVersion=true

Details

Impact

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.

There is no known path for an attacker to induce such an exception to be thrown, thus they must rely on an application to throw such an exception. The OP has also identified that during the call to sessionDestroyed, the getLastAccessedTime() throws an IllegalStateException, which potentially contrary to the servlet spec, so applications calling this method may always throw and fail to log out. If such an application was only tested on a non clustered test environment, then it may be deployed on a clustered environment with multiple contexts and fail to log out.

Workarounds

The application should catch all Throwables within their SessionListener#sessionDestroyed() implementations.

Is GHSA-m6cp-vxjx-65j6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.eclipse.jetty:jetty-server, and gives you the command that fixes it.

More advisories for org.eclipse.jetty:jetty-server

  • HighCVE-2024-7708Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests · 22 Jul 2026
  • MediumCVE-2026-6790Eclipse Jetty: HTTP Authority/Host mismatch · 22 Jul 2026
  • MediumCVE-2026-10051Eclipse Jetty: Cross-Request Leakage for trailers on HTTP/1.1 keep-alive connections · 22 Jul 2026
  • HighCVE-2026-1605The Eclipse Jetty Server Artifact has a Gzip request memory leak · 5 Mar 2026
  • HighCVE-2024-13009**UNSUPPORTED WHEN ASSIGNED** GzipHandler causes part of request body to be seen as request body of a separate request · 8 May 2025
  • MediumCVE-2024-8184Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks · 14 Oct 2024
All 29 advisories for org.eclipse.jetty:jetty-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.