Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: Cookie not expiring...

Subject: Re: Cookie not expiring...
Date: 17 Aug 2005 13:24:42 -0000
Hi All,

I think the case is only with Cookieless sessions.
"Session ID values used in cookieless sessions are recycled by default. That 
is, if a request is made with a session ID that has expired, a new session is 
started using the System.Web.SessionState.HttpSessionState.SessionID supplied 
with the request. This behavior can result in the unwanted sharing of session 
data when a link that contains a cookieless 
System.Web.SessionState.HttpSessionState.SessionID is shared with multiple 
browsers perhaps through a search engine or other means. You can reduce the 
possibility of session data being shared by multiple clients by disabling the 
recycling of session identifiers. To do this, set the 
regenerateExpiredSessionId attribute of the <sessionState> configuration 
element to true. This will result in a new session id being generated when a 
cookieless session request is made with an expired session id."

But the most important thing that was missed is
"If the request made with the expired session id is made using the HTTP POST 
method, then any posted data will be lost when regenerateExpiredSessionId is 
true, as ASP.NET performs a redirect to ensure that the browser has the new 
session identifier in the URL."

And in .NET, you call the 
System.Web.SessionState.HttpSessionStateProvider.Abandon method when a user 
logs out. This reduces the potential for an unwanted source using the unique 
identifier stored in the URL to retrieve private data stored in the session for 
a user.

Regards,

Dharmesh Mehta
Technology Cell,
Mastek Ltd.

<Prev in Thread] Current Thread [Next in Thread>