CWE
362 367 613
Advisory Published
Updated

GHSA-9j94-67jr-4cqj: Race Condition

First published: Thu May 08 2025(Updated: )

## Summary When using the `Rack::Session::Pool` middleware, simultaneous rack requests can restore a deleted rack session, which allows the unauthenticated user to occupy that session. ## Details [Rack session middleware](https://github.com/rack/rack-session/blob/v2.1.0/lib/rack/session/abstract/id.rb#L271-L278) prepares the session at the beginning of request, then saves is back to the store with possible changes applied by host rack application. This way the session becomes to be a subject of race conditions in general sense over concurrent rack requests. ## Impact When using the `Rack::Session::Pool` middleware, and provided the attacker can acquire a session cookie (already a major issue), the session may be restored if the attacker can trigger a long running request (within that same session) adjacent to the user logging out, in order to retain illicit access even after a user has attempted to logout. ## Mitigation - Update to the latest version of `rack-session`, or - Ensure your application invalidates sessions atomically by marking them as logged out e.g., using a `logged_out` flag, instead of deleting them, and check this flag on every request to prevent reuse, or - Implement a custom session store that tracks session invalidation timestamps and refuses to accept session data if the session was invalidated after the request began. ## Related This code was previously part of `rack` in Rack < 3, see <https://github.com/rack/rack/security/advisories/GHSA-vpfw-47h7-xj4g> for the equivalent advisory in `rack` (affecting Rack < 3 only).

Affected SoftwareAffected VersionHow to fix
rubygems/rack-session>=2.0.0<2.1.1
2.1.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of GHSA-9j94-67jr-4cqj?

    The severity of GHSA-9j94-67jr-4cqj is considered high due to the risk of session fixation allowing unauthorized access.

  • How do I fix GHSA-9j94-67jr-4cqj?

    To fix GHSA-9j94-67jr-4cqj, upgrade the rack-session middleware to version 2.1.1 or higher.

  • Who is affected by GHSA-9j94-67jr-4cqj?

    Applications using the Rack::Session::Pool middleware prior to version 2.1.1 are affected by GHSA-9j94-67jr-4cqj.

  • What does GHSA-9j94-67jr-4cqj allow an attacker to do?

    GHSA-9j94-67jr-4cqj allows an unauthenticated user to occupy a deleted session, potentially gaining unauthorized access.

  • When was GHSA-9j94-67jr-4cqj published?

    GHSA-9j94-67jr-4cqj was published on May 4, 2022.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203