Skip to main content

Preventing Session Hijacking

What is Session Hijacking
Session Hijacking is an attack that when an attacker takes control of an already validated user.
When an application authenticates a user it assigns a random string called sessionID to the validated user and that sessionID is traversed every time there's an interaction between the logged in user and the application. Generally the sessionID remains valid till the user logs out. After that the particular sessionID becomes invalid. So sessionIDs are very important concept in session based application. SessionIDs itself can be captured by following ways:
  • Prediction
  • Capture
  • Fixation
If an adversary takes hold of the sessionID he can impersonate the real valid user and the application won't have any way to differentiate between the real user and the attacker. This is the general concept of Session Hijacking.

Prevention to Session Hijacking
A combination of following methods can prevent the problem:
  • Use of a long random number or string as the session key. This reduces the risk that an attacker could simply guess a valid session key through trial and error or brute force attacks to prevent Prediction.
  • The sensitive application (such as login page) must use secure communication (such as SSL) to avoid sniffing of session identifiers and user credentials to mitigate Capture.
  • Also the session identifiers can be captured if the application has the XSS (Cross Site Scripting) flaw. So the application must be not vulnerable to XSS to prevent Capture.
  • The application must expire the session identifiers after logout and regenerate new session identifiers after the user ‘authentication only’. This will mitigate the Fixation problem.
  • Register some other variables like some secret random no. like hash of user agent details of the browser can be also fruitful. As there is very rare chance that the user will move to another browser while performing an action while currently logged in to the application. Store that hash of the browser along with sessionID onto the server and match it with every incoming request of the user. If matches proceed , if not, there's high chance that somebody other has logged in currently. Invalidate the session.
  • Mark the cookies as 'HTTPOnly' so that they can't be accessed through XSS.
Although there's no single and sufficient methods to mitigate the problem, above methods and an aware user can save themselves from the attack.

Comments

Chintan Dave said…
Dude, apart from prediction, capture (i.e. hijacking) and fixation, there is one more arena that could be explored - you missed out brute forcing :P :P.

If it sounds irritating, you dont have any option, but to bear with this comment :D
July 15, 2009 at 12:55 PM
Post a Comment

Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T...
1 comment
Read more

'Information Leakage-Improper Error Handling' dropped

From Owasp Top 10 2010 List, the issue 'Information Leakage-Improper Error Handling' has been dropped. But it's not the final list,its child release actually. Bu I feel it shouldn't be set aside because its still the one of the prevalent issues these days. That's why I mailed to Dave Wicher: Hi Dave, Excellent work, Congrats! Just one little query- Don't you think that Information Leakage & Improper Error Handling still deserves to be in Top 10? Dave replied: This topic is clearly a very prevalent issue that deserves attention by most organizations. However, the typical impact of such a flaw is usually very low. Therefore, the overall risk of this type of flaw is lower than the other items in the top 10, which is why it was replaced in this update with one of the 2 new items. Regarding dropping Info Leak/Error handling - It is incredibly prevalent, no question. But their impact is typically very low, so the overall risk is low, which is why it fell out of t...
3 comments
Read more

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the devic...
1 comment
Read more