Skip to main content

Google Images Search Open Redirection Vulnerability

Yes, I know Open Redircetion Vulnerablities are abundant on various sites and can be found easily. However I take this opportunity to populate my blog with various flaws found by me just for record. Who cares thousands of redirection flaws found on many sites but when the vendor is so prominent and didn't pay attention to the problem even when notified to them many days back..and still remains unfixed..it is surprising.
The Open redirection vulnerability may be an easily dectectable one but when it comes to exploit it..it can lead to serious consequences like..misdirecting users to any malicious site ,which in turn, can download malwares on user's PC, Phishing attack or even DOS in certain cases and that too on cost of Vendor's reputation. That's why waiting for the vendor to fix it I am going to publish it here.

The following URL:
http://images.google.co.in/imgres?imgurl=http://aaa.com/a.jpg&imgrefurl=http://www.aaa.com
can be used to redirect a user to another site created by the attacker.
It works only when both parameters are supplied ‘imgurl’ and ‘imgrefurl’.
Threat: Phishing.
Proof of Concept: -
The following URL will redirect a user to another site(eg: rediff.com).
The URL can be used for Phishing attack
http://images.google.co.in/imgres?imgurl=http://rediff.com&imgrefurl=http://rediff.com/
The link above can be used to make user visit any Phishing site as user will see name of 'google' in the URL and easily follow it.Even it can be encoded an d provided to the user for more sophisticated attack.

Had it been one parameter attack then DOs can also be performed like:
http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl= http://images.google.co.in/imgres?imgurl=http://images.google.co.in/imgres?imgurl=http://anymalicioussite.com
Now although the previous link does not perform a DOS, similar trickcan practically perform a DOS attack, causing the client to endlessly wait for the reply.

Comments

vinnu said…
This is a latest redirect i found in rediff:


http://auctions.rediff.com/search.php?q=3;URL=http://loxian.co.cc%22%20http-equiv=%22Refresh%22%20%3E

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: