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.

Comments

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. T...

'Information Leakage-Improper Error Handling' dropped

From Owasp Top 10 2010 List, the issue 'Information Leakage-Improper Error Handling' has been dropped. But it's not the final list,its child release actually. Bu I feel it shouldn't be set aside because its still the one of the prevalent issues these days. That's why I mailed to Dave Wicher: Hi Dave, Excellent work, Congrats! Just one little query- Don't you think that Information Leakage & Improper Error Handling still deserves to be in Top 10? Dave replied: This topic is clearly a very prevalent issue that deserves attention by most organizations. However, the typical impact of such a flaw is usually very low. Therefore, the overall risk of this type of flaw is lower than the other items in the top 10, which is why it was replaced in this update with one of the 2 new items. Regarding dropping Info Leak/Error handling - It is incredibly prevalent, no question. But their impact is typically very low, so the overall risk is low, which is why it fell out of t...

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the devic...