|
|||||||||||
|
RE: How to protect against cookie stealing?
From: Ingo Struck <ingo(at)ingostruck.de>
Date: Thu Jul 24 2003 - 08:33:42 EDT
> The application does not associate the cookie to any session-specific
If an application doesnt do that, then it's of course a poor app... What we use for this within OCL (OWASP Common Library, see http://sourceforge.net/projects/owasp for the source and http://beta.owasp.org/development/ocl for an overview) is:
See org.owasp.aux.servlet.ServletUtil::checkUnprivileged and org.owasp.aux.servlet.ServletUtil::checkPrivileged for some java code. > Historically I have believed that having the application associate
The problem thus has to be solved from two sides: a) implement the known technical countermeasures against the simplest forms of session stealing (if there's a proxy inbetween you can at least dramatically isolate the circle of possible attackers) b) tell the users who are "locked out" due to these countermeasures why and what they should do to be worth considered for "secure" access Note, however that these countermeasures against session stealing are not 100% fool-proof (they still allow for MITM attacks), but they are not limited to Cookie-based sessions only. Combined with a decent security logging they help at least to reveal most of the trials to steal SIDs. Kind regards Ingo Struck --- Ingo Struck OWASP http://owasp.orgReceived on Thu Jul 24 13:02:08 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:54 EDT |
||||||||||
|
|||||||||||