Title

The Tomcat server must invalidate session identifiers upon user logout or other session termination. (Cat II impact)

Discussion

If communications sessions remain open for extended periods of time even when unused, there is the potential for an adversary to hijack the session and use it to gain access to the device or networks to which it is attached. Terminating sessions after a logout event or after a certain period of inactivity is a method for mitigating the risk of this vulnerability. When a user management session becomes idle, or when a user logs out of the management interface, the application server must terminate the session.

Check Content

Check the web.xml configuration file for the following lines: <session-config> <session-timeout>1</session-timeout> </session-config> The session-timeout setting should be set to an organization defined timeout. If the sess-timeout is not set to the organization defined timeout or is defined to ridiculously high value (i.e. 600000 minutes), this is a finding.

Fix Text

Configure the application server to terminate administrative sessions upon logout or any other organization- or policy-defined session termination events.

Additional Identifiers

Rule ID: SV-46702r3_rule

Vulnerability ID: V-35415

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.