Skip to content
StrikeOps

Session Not Invalidated on Logout

MediumTypical severity Web applications and APIsCWE-613

01Description

Session tokens remained valid on the server after the user logged out, or sessions did not expire after a reasonable period of inactivity.

02Impact

A session token captured by an attacker, for example from a shared computer, browser history, proxy logs or malware, remains usable after the user believes they have logged out.

03Severity

Typically

Medium

Typically Medium. Medium for most applications. Higher for applications handling financial or health data or commonly used on shared devices.

04How to verify

  1. 1Capture a valid session token, log out, then replay a request using the old token.
  2. 2Leave a session idle beyond the expected timeout and test whether it is still accepted.
  3. 3Check whether password changes invalidate other active sessions.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Invalidate session tokens on the server at logout, not only in the browser.
  2. 2Enforce idle and absolute session timeouts appropriate to the data handled.
  3. 3Invalidate all sessions on password change and offer users a 'sign out everywhere' option.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo