Skip to main content

Mist around Clickjakcing

These days there is much noise about a new term "Clickjacking".

I think the term is new in itself not the the way it executes. Clickjacking is a form of UI redressing attack and equivalent to XSRF attack. Like XSRF attack it also uses the credentials of already authenticated user to execute the request successfully because the server can't differentiate between user's request and an extranal hacker's link. Then came the mitigation to this XSRF attack to use page-nonces,randomly generated one time hashes or values, which are included in every page request-response uniquely.

The main risk imposed by Clickjacking is the ability to bypass nonce-based XSRF defence. In the Clickjacking attack, the user interacts directly with the target Web page, which is visually hidden, so all transactions include a valid nonce and the attack is left undetected.Clickjacking has proved that our theory about nonce-based defense and where its weaknesses lies is true.The main risk imposed by the clickjacking attack is the ability to bypass nonce based XSRF defence, which is considered the most robust protection against XSRF attacks.
Since the vulnerability that allows clickjacking attacks resides in client software(Web Browsers) and not in Web applications, there is no complete solution except of presenting fixes to the vulnerable platforms.
Major vendors products are said to be affected from this vulnerbility.That's why security researchers had deferred their presentation on how to exploit it after receiving request form the vendor.

Web Keys can be used to mitigate the problems to some extent.Complete defence is still awaited.

Imperva paper gives a great detail of the issue.


Popular posts from this blog

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…

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…

Insecure protocols

Some basic insecure protocols and risk associated with them: