|
|||||||||||
|
AW: JRun: The Easiness of Session Fixation
From: Javor Evstatiev <Javor.Evstatiev(at)d-con.com>
Date: Sat Mar 01 2003 - 15:13:49 EST
I can talk surely only about php, but this should work also in java:
cheers
-----Ursprüngliche Nachricht-----
Hi all The the Session-ID Fixation paper available from http://www.acros.si/papers/session_fixation.pdf mentions that JRun accepts abritrary Session-ID's and create new sessions with the proposed Session-ID. This means that it is possible to send the following URL http://foo/bar?jsessionid=foo123 and the JRun server will accept and use the proposed Session-ID (foo123). Furthermore the server will set a cookie in users browser with the proposed Session-ID! Using this technique, it is much easier to exploit this kind of attack and to enter in other's web application sessions. Is anybody aware of a vendor patch or another workaround? Is it possible to enforce the server to create a new Session-ID? Thanks a lot Christoph Received on Sat Mar 1 15:24:46 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:49 EDT |
||||||||||
|
|||||||||||