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: Whitepaper "SESSION RIDING - A Widespread Vulnerability in Today's Web Applications" |
|---|---|
| Date: | Thu, 23 Dec 2004 11:55:15 -0600 |
Perhaps the applications that are more likely to be exploited are those that the user stays logged in and that periodically refreshes theirselves, like webmails. I don't see them as a huge threat for systems like Internet Bankings, for example.
I general I would agree. In experience I'm still surprised how often systems have fundamentally broken session management, or it's a service provider model and the first tier 'client' has control of session timeout and sets it to infinite for their 'clients'. SP blames client for this practice and client says security is SP issue and no resolution in the end. Or my all time favorite is the billpay app with the session token cookies that to this day I believe still go 1078, 1086, 1097, 1099, [....] Thank goodness I read that paper those Bindview guys wrote on doing 3 Dimensional modeling of IP space. I stole some perl scripts from Rogan Dawes and tried that out, otherwise I might have missed that one. It was not some increment-by-one that could be observed by a tester of my skill each time I'd log in and out. It would jump by four or six or sometimes ten because they had cryptographically obscured the value incrementation due to the fact other people were logging in and out of the application at the same time. Clever. I recommended they take the session token (1111) + username (aevans) and encrypt it (1111nrinaf) but they did not listen to me. U2FmZSBhbmQgSGFwcHkgSG9saWRheXMh RG9uJ3QgdGFrZSB0aGlzIHRvbyBzZXJpb3VzbHkh Everyone take care, Arian The information transmitted in this e-mail is intended only for the addressee and may contain confidential and/or privileged material. Any interception, review, retransmission, dissemination, or other use of, or taking of any action upon this information by persons or entities other than the intended recipient is prohibited by law and may subject them to criminal or civil liability. If you received this communication in error, please contact us immediately at 816.421.6611, and delete the communication from any computer or network system.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: (robust web apps) Whitepaper "SESSION RIDING - A Widespread Vulnerability in To day's Web Applications", Evans, Arian |
|---|---|
| Next by Date: | Re: Article - A solution to phishing, Michael Silk |
| Previous by Thread: | RE: Whitepaper "SESSION RIDING - A Widespread Vulnerability in Today's Web Applications", Scovetta, Michael V |
| Next by Thread: | Is this exploitable?.., Benjamin Livshits |
| Indexes: | [Date] [Thread] [Top] [All Lists] |