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. |

| Subject: | Re: Session Hijacking over HTTP |
|---|---|
| Date: | Wed, 19 Mar 2008 09:41:56 +1100 |
To protect session cookies you can set the cookie property: to send only over SSL. Also, regenerate SID after the user has authenticated to the application - this will safe guard their account in case the SID was compromised prior to authentication. The SID itself should be custom generated and include a digest of the following client properties (can be more, this is the minimum): IP address, port number, agent string. This way a session will be tied to a particular machine and user. This is the industry best practice. Don't worry about building "custom browser or enterprise solution" since it will only complicate things and get you hacked, remember the KISS principle. This is of course excluding the fact that it sounds like a complete bandaid solution to a problem that should be solved at design or implementation stage of the SDLC. In regards to the "trusted channel" - SSL is about as trusted a it gets (excluding my uber army of specially trained carrier pidgins of course). Serg On Tue, Mar 18, 2008 at 10:21 PM, 11ack3r <11ack3r@gmail.com> wrote:
Hello Everyone, I was curious to know how would webmail portals like gmail.com and yahoo.com protect their users from session hijacking when they use HTTP after authentication. As I see it is trivial to capture traffic over the wire including session cookies. In such a case can an attacker just reuse the session cookies in his/her browser and compromise the user account? WHat is the best way to protect session cookies from hijacking esp. due to network eavesdropping? Of course HTTPS can also be bypassed with MITM attacks if users ignore browser warnings. Looking forward to some knowledge here. Cheers!! ------------------------------------------------------------------------ This list is sponsored by: Cenzic Need to secure your web apps NOW? Cenzic finds more, "real" vulnerabilities fast. Click to try it, buy it or download a solution FREE today! http://www.cenzic.com/downloads ------------------------------------------------------------------------
------------------------------------------------------------------------ This list is sponsored by: Cenzic Need to secure your web apps NOW? Cenzic finds more, "real" vulnerabilities fast. Click to try it, buy it or download a solution FREE today! http://www.cenzic.com/downloads ------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Pentesting tools for Linux IP Tables, Jamie Riden |
|---|---|
| Next by Date: | Re: anonymous Zonetransfer (AXFR) exploatation, Radu Oprisan |
| Previous by Thread: | Re: Session Hijacking over HTTP, Gleb Paharenko |
| Next by Thread: | RE: Session Hijacking over HTTP, Shenk, Jerry A |
| Indexes: | [Date] [Thread] [Top] [All Lists] |