Re: Hijacking URL Encoded Session IDs using Referer Logs

>
> Many (most?) application servers use URL encoded session IDs when the

A big problem is people hear the buzzword cookie and security and think every website can steal every cookie from every site they ever visited. This isn't true unless they exploit some browser flaw. The only risk a cookie has is if it is stolen (*usually* through xss attacks) Obviously some people will disable cookies. A *better* approach(if no cookies are used) would be to tie the session (if in url)
to the users ip address. This way if userb enters in this url they can't do anything (unless they share a proxy so this isn't always safe).

Always lots of factors.

> server vendors stop allowing URL encoded session IDs by default.

Another reason why a cookie is better to use.  

> Does hotmail or yahoo use URL session IDs? E-mail someone a link to

Yes I see this maybe once a month or two for people using smaller free webmail companies I simply enter in the referer and boom get in there mailbox.

• zeno

>
> Also a good reason to use HTTPS.
Received on Mon Nov 25 16:36:49 2002

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related securityfocus.com Links bugtraq certification focus-bsd focus-ids focus-ih focus-linux focus-ms focus-sun focus-unix-other focus-virus forensics incidents libnet linux-secnews ms-secnews pen-test secpapers secprog sectools secureshell security-basics securityjobs sf-news vuln-dev webappsec Request more information about Pantek