Skip to main content

Implementing HSTS

Everyone know the what HSTS (HTTP Strict Transport Policy) does- It instructs the browsers to load a website over HTTPS no matter what. You cannot load a website on the http. When you hit a website, eg, http://example.com, the server returns ‘Strict-Transport-Security’ Header that tells that now onwards the website must be loaded over https.
We know the issue related to redirecting a site from http to https, the 302/ 301 redirects the site to its secure scheme by loading the https://expmale.com when user hits http://example.com . The issue here is the response from the first request which loads on http can be modified and contents can be replaced with some phishing ones. Still a large no. of websites do this redirection, one classic example is American Express. When you try to access www.americanexpress.com first time , it redirects you to https://www.americanexpress.com :


The website first loads as http and then makes a 301 redirect and loads again over https. The below pic will make it clearer:


Now let’s examine the following website (Facebook). Try accessing http://facebook.com and it loads on https://facebook.com . But there’s a difference here, instead of making 301/ 302 redirect the Facebook site makes a 307 redirect which is an internal redirect:

The 307 instructs that the browser is not going to make the first request itself on http, instead it will make the first request over https. The browser has refused to make any connection on insecure protocol http. Let’s examine the response:

You can see the HSTS header in the response:


All the sites which need to be loaded over https by default must be submitted to https://hstspreload.appspot.com/ site. This site is maintained by chrome and has a list of domains which needs to be loaded over https by default. That means, when the browser is shipped, your site will be a part of the list where https is by default.


Comments

Popular posts from this blog

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

Insecure protocols

Some basic insecure protocols and risk associated with them: