|
|||||||||||
|
RE: Session Fixation
From: Information Security <InformationSecurity(at)federatedinv.com>
Date: Mon Mar 31 2003 - 08:19:14 EST
There are, IMHO, at least two other mitigation strategies, or points to consider: First, make sure applications have a "logout" option, and train users to use it when they're done. It's a mitigation strategy for this and other session vulneraiblities (XSS, etc) to at least reduce the window of opportunity. Second, make sure the account password change page (and hint pages, if applicable) require the user to supply the old password as well as the new. Prevents the hijacked session from changing the password and essentially creating the back door.
-----Original Message-----
Thanks for posting, this is an excellent article. One cavaet is with respect to binding the session ID to the browser's network address. There are some proxy servers that swap IP addresses between HTTP requests. In this case, binding to the exact IP address can cause a valid session to be orphaned. Gary
St. Clair, James wrote:
-- Gary Gwin http://www.cafesoft.com ***************************************************************** * * * The Cafesoft Access Management System, Cams, is security * * software that provides single sign-on authentication and * * centralized access control for Apache, Tomcat, and custom * * resources. * * * *****************************************************************Received on Mon Mar 31 10:37:38 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:49 EDT |
||||||||||
|
|||||||||||