Skip to main content

More mist around Clickjacking :)

The more I read, the more theories I get on the topic. Everybody has his own theories about Clickjacking.There's no consensus on the issue. Clickjacking for one is URL rewriting for another,simple hyperlink jump for another. Even there are contradiction by the people on Aditya's PoC on clickjacking in Chrome browser. Even on Hackademix.net Giorgio Maone has took the PoC lilghtly. That again increased the mist around the issue.
Then what is the real clickjacking? In facts, with "Clickjacking" we designate a class of attacks (also known as "UI Redressing") which consist in hiding or disguising an user interface element from a site you trust in a way which leads you to click it without knowledge of what you're exactly doing.
That's what Aditya showed in his PoC. When you click the link you are redirected to another site of attackes' choice without knowledge of users. When hovering the mouse over link it shows the intended name of the site, there's no way of doubt but clicking it once takes user to another site.
Google accepted it,others not accepting it.
Mozilla assumes it as URL rewriting via onClick event handler. I wrote back to Mozilla:

Dear Mozilla Team,

Thanks for the quick response.

Regarding the first example (click.html) I have sent , the exploit is not the issue but the browser executes the exploit is the real issue.Google has accepted the exploit being executed in their chrome browser as vulnerable to clickjacking ( you might have gone through several articles regarding it).

I used the same exploit to test with your latest Firefox 3.1 beta 2, I found that it’s executing successfully. I used same exploit with Opera 9.63 and was executing in that browser.
That’s why I brought it in your notice.
Anyways everyone has his own theory. I am not claiming myself to be expert on the issue but as Mozilla said to me:

"Clickjacking is when a user clicks on what they think is a button on a random site (i.e. attacker's site in the URL bar) but they are actually clicking buttons on another site like their bank without realizing it."


And in my second example I did same thing. I used iframe to load Google.com and exactly over the search button using div tag I loaded a blank invisible transparent frame. Clicking on 'search' button user is actually clicking on the 'invisible frame' and gets redirected to another malicious site. That confirms Mozilla's aforementioned definition above. This is an example of Graphic Overlaying Clickjacking. There's no need of using Javascript to execute it. So even 'NoScript' Plugin won't mitigate it. Only thing that can prevent it is Frame Busitng codes that will prevent loading any frame in the web page at all!

But again I am getting different theories from different vendors about clickjacking. So I will now just sit back and wait for the final concluding clickjacking definition and then only go for further research.

Comments

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

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

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.