Skip to main content

ForceHTTPS:Strict-Transport-Security

Use of HTTPS for securing the data in transmission from eavesdropping is well known.
The user can be sure that the data he is submitting is going over encrypted channel and is secure from sniffing.
Although it's secure but few factors can still be considered as major lapse in implementing HTTPS securely.All modern web browsers are willing to compromise the security of sites that use HTTPS in order to be compatible with sites that deploy HTTPS incorrectly.For example, if an active attacker presents a self-signed certificate, web browsers permit the user to click through a warning message and access the site despite the error.Certificate Errors happen due to Common-Name mismatch between the certificate name and hosting server;Self-signed certificates or expired certificates.This behavior compromises the confidentiality of the site's Secure cookies, which often store a second factor of authentication, and allows the attacker to hijack a legitimate user's session.
End-user being a novice in security knowledge will happily choose to accept the warning message and tend to perform his action.

A new technique for thwarting this kind of flaws has been proposed by Adam Barth and Collin Jackson as 'ForceHTTPS'.By setting a ForceHTTPS cookie, a site owner asks the browser to treat HTTPS errors as attacks, not as simple configuration mistake.
ForceHTTPS causes a browser to do the following:

1.All errors like self-signed certificate warning or common-name mismatch will terminate the SSL Session.

2.Non-HTTPS connections are redirected to HTTPS.

3.Attempts to embed insecure (non-HTTPS) content into
the site fail with network errors.

But the ForceHTTPS protects you against the active/passive sniffing and improper configured web certificates.
It does not address threats like Phishing and Malware/Browser Vulnerabilities.

Paypal has alreday implemented it and currently Firefox,Goolge Chrome and Noscript is implementing it.
ForceHTTPS uses 'Strict-Transport-Policy'(STS) header to implement the security.

STS server returns the following response header:

"Strict-Transport-Security" ":" "max-age" "=" delta-seconds [ ";" "includeSubDomains" ]

For more info visit:https://crypto.stanford.edu/forcehttps/


Comments

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

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 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