V-288191

Discussion

Captured sessions can be reused in replay attacks. Applications that use communications sessions must invalidate session identifiers (IDs) upon user logout or other session termination limits to prevent adversaries from capturing and continuing to employ previously valid session IDs. This includes, but is not limited to, web-based applications and service-oriented architectures (SOAs). Session IDs are tokens generated by web applications to uniquely identify an application user's session. Applications will make application decisions and execute business logic based on the session ID. Unique session IDs are the opposite of sequentially generated session IDs that can be easily guessed by an attacker. Unique session IDs help to reduce predictability of said identifiers. When a user logs out, or when any other session termination event occurs, the application must terminate the user session to minimize the potential for an attacker to hijack that user session. Note: This only applies to communications protection for the application session not the network packet.

Check Content

Review the application documentation and deployed configuration to determine whether the application invalidates session identifiers upon user logout or other session termination.

If the application does not invalidate session identifiers upon user logout or other session termination, this is a finding.