Skip to main content

How cookie can leak

Today I was having a chat with my friend Vaibhav about few vulnerabilities in one of the applications. In order of that he asked me it's really necessary to mark cookie as "Secure". Well, depends...if your whole application is on https then you should always go for "Secure" attribute. Cookies set with the "Secure" keyword will only be sent by the browser when connecting by a secure means (HTTPS). Apart from that there is no distinction - if "Secure" is absent, the cookie may be sent over an insecure connection.

We have seen a lot of cases where the cookie is leaked and sent over from https to http:

1. If your page contains mixed contents, ie. if you are including some links that is on http then the cookie may be leaked. For example, if your application uses url https://example.com and you are including someother links in the page using http://, the browser may warn you as "this page contains both secure and nonsecure items".

2. If you are visiting page with https:// link but you click on a third party link which is on http:// that may leak the cookies.

3. The browser may cache the cookies if not marked as secure.

So mainly there are 4 conditions:

* HTTP Cookie, with "Secure" will be returned only on HTTPS connections
* HTTPS Cookie, with "Secure" will be returned only on HTTPS connections
* HTTP Cookie, without "Secure" will be returned on HTTP or HTTPS connections
* HTTPS Cookie, without "Secure" will be returned on HTTP or HTTPS connections (could leak secure information)

So, HTTP Cookies can be read by HTTP or HTTPS. HTTPS Cookies can only be read by HTTPS, that is if you set Secure = True on the cookie.
Also how and when to setup "Secure" flag, you can visit my last posts-this and this

References:
http://www.w3.org/Protocols/rfc2109/rfc2109
http://stackoverflow.com/questions/2163828/can-cookies-set-using-http-be-read-using-https

Corrections,if any, is always appreciated!

Comments

Vaibhav said…
Hi Nilesh,

I had a discussion with the client and we came to the discussion that the application only has HTTPS port open i.e 443 and each and every request of the application goes through HTTPS as no HTTP port 80 is being used. Is it still necessary to secure the cookies.

So your point helped me to answer the question that "Non Secure cookies can be cached in the memory" :) and that helped me to push client to implement Secure TAG to all the cookie value.

Thanks
Vaibhav
March 11, 2011 at 7:20 PM
Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more

Hijacking SSL

SSL has been in centerstage of researches as well as attacks for quite long time. Last year in a conference in Germany researchers showed how to generate duplicate certificates exploiting MD5 hashing to break SSL. Later in Black Hat, Maxie showed how to exploit a field in SSL certificates to sign an own forged certificate to present it to the client. The main feature of this attack was that the client will never get any warning dialog box by the browser and subsequently the hacker doing an MITM can see the conversation between the client and server. The client will even get a PADLOCK sign to be assured that all things are going via encryption, but in reality it's not. Maxie released a tool SSLStrip to carry out these attacks. The tool has been used by many researchers around the world to carry out the attacks. They all used Unix machines as many open source utilities makes it easier to run the tool on it. My attempt was to run the tool on a Windows machine. It has been never easy t...
4 comments
Read more