Difference between revisions of "Open redirect"

From OWASP
Jump to: navigation, search
m (Avoidance and mitigation)
(Undo revision 126434 by Robert Hof (talk))
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Overview==
+
{{Template:Stub}}
 +
{{Template:Vulnerability}}
 +
 
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 
 +
[[ASDR_TOC_Vulnerabilities|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.
 
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.
  
{{Template:Stub}}
+
'''Consequences'''
 +
 
 +
[[Phishing]]
 +
 
 +
'''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
 +
 
 +
Faked link: http://www.vulnerable.com/security/advisory/23423487829/../../../redirect.asp%3F%3Dhttp%3A//www.facked.com/advisory/system_failure/password_recovery_system
 +
 
 +
==Related [[Attacks]]==
 +
 
 +
* [[Attack 1]]
 +
* [[Attack 2]]
 +
 
 +
 
 +
==Related [[Vulnerabilities]]==
 +
 
 +
* [[Open forward]]
 +
 
 +
==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]]==
 +
 
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 
  
==Consequences ==
+
==References==
  
[[Phishing]]
+
TBD
  
==Exposure period ==
+
[[Category:FIXME|add links
  
==Platform ==
+
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
  
==Required resources ==
+
Availability Vulnerability
  
==Severity ==
+
Authorization Vulnerability
  
 +
Authentication Vulnerability
  
==Likelihood of exploit ==
+
Concurrency Vulnerability
  
 +
Configuration Vulnerability
  
==Avoidance and mitigation ==
+
Cryptographic Vulnerability
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)
+
Encoding Vulnerability
  
==Discussion ==
+
Error Handling Vulnerability
  
 +
Input Validation Vulnerability
  
==Examples ==
+
Logging and Auditing Vulnerability
  
http://www.vulnerable.com?redirect=http://www.attacker.com
+
Session Management Vulnerability]]
  
==Related problems ==
+
__NOTOC__
  
* [[Open forward]]
 
  
 +
[[Category:OWASP ASDR Project]]
 
[[Category:Vulnerability]]
 
[[Category:Vulnerability]]

Revision as of 12:36, 16 March 2012

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): 03/16/2012

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

Phishing

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

Faked link: http://www.vulnerable.com/security/advisory/23423487829/../../../redirect.asp%3F%3Dhttp%3A//www.facked.com/advisory/system_failure/password_recovery_system

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