This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Open redirect"
(→Examples) |
|||
| Line 43: | Line 43: | ||
==Related [[Controls]]== | ==Related [[Controls]]== | ||
| − | * To avoid the open redirect vulnerability parameters of the application script/program must be validated before sending 302 HTTP code (redirect) to the client browser. | + | * To avoid the open redirect vulnerability, parameters of the application script/program must be validated before sending 302 HTTP code (redirect) to the client browser. |
| − | |||
| − | |||
| + | The server must have a relation of the authorized redirections (i.e. in a database). | ||
==Related [[Technical Impacts]]== | ==Related [[Technical Impacts]]== | ||
Revision as of 13:19, 27 February 2009
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Last revision (mm/dd/yy): 02/27/2009
Vulnerabilities Table of Contents
Description
An open redirect is an application that takes a parameter and redirects a user to the parameter value without any validation. This vulnerability is used in phishing attacks to get users to visit malicious sites without realizing it.
Consequences
Platform All web platforms affected
Risk Factors
TBD
Examples
http://www.vulnerable.com?redirect=http://www.attacker.com
The phishing use can be more complex, using complex encoding:
Real redirect: http://www.vulnerable.com/redirect.asp?=http://www.links.com
Related Attacks
Related Vulnerabilities
Related Controls
- To avoid the open redirect vulnerability, parameters of the application script/program must be validated before sending 302 HTTP code (redirect) to the client browser.
The server must have a relation of the authorized redirections (i.e. in a database).
Related Technical Impacts
References
TBD
