Skip to main content

Open Redirection Vulnerability

An open redirect is a vulnerability that exists when a script allows redirection
to an external site by directly calling a specific URL in an unfiltered,unmanaged fashion, which could be used to redirect victims to unintended,malicious web sites.

An open redirect is a very simple vulnerability to exploit.

Consider the following example:
http://www.trustedbank.com/page.redir?target=http://www.anygovtsite.gov/

This is a well-intended URL that takes users to any other trusted site.

But this can be abused in one of the following ways:


The URL can be used for Phishing attack-

http://www.trustedbank.com/page.redir?target=http://www.duplicatesite.com/
The user visiting the trusted bank website will get redirected to the phishing site/malware site.
This can hurt the reputation of organization causing business loss.


This can be further escalated by mal-forming the link. Something like

the following can be used to cause the Denial of Service Attack:

http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=
http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=
http://www.trustedbank.com/page.redir?target=http://www.trustedbank.com/page.redir?target=......
http://www.trustedbank.com/page.redir?target=http://anymalicioussite.com


Now although the previous link does not perform a DOS, similar trick can practically perform a DOS attack, causing the client to endlessly wait for the reply.

Prevention:

To prevent phishing attacks, or redirection to browser attackers and malware hosts, site
administrators must lock down their redirects.
Again, if site operators must absolutely use redirection, the use of intermediary pages advising
users of the redirection is imperative.
Alternatively, allow redirection only to specifically white-listed sites. For example, administrators could limit linking to external sites only when a user actually clicks on the link while on the main site, thus preventing links in e-mail or instant messages from working.

Few times before Google Image Search was susceptible to this was exploited by phishers.
Cisco web site is also susceptible to this vulnerability.

Comments

minishach said…
Really good. You made a small yet understandable article which gives any beginner a good understanding about the topic. I really like it. Thanks for your wonderful effort.

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

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

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be