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 "Execution After Redirect (EAR)"
(Created page with "{{stub}} {{Template:Attack}} Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' ==Overview== Execution After Redirect (EAR) is an attack whe...") |
|||
| Line 11: | Line 11: | ||
Using most proxies it is possible to ignore redirects and display what is returned. In this test we use Burp Proxy.<br> | Using most proxies it is possible to ignore redirects and display what is returned. In this test we use Burp Proxy.<br> | ||
# Intercept request https://vulnerablehost.com/managment_console | # Intercept request https://vulnerablehost.com/managment_console | ||
| − | # | + | # Send to repeater. |
# View response. | # View response. | ||
Revision as of 17:10, 9 January 2013
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
- This is an Attack. To view all attacks, please see the Attack Category page.
Last revision (mm/dd/yy): 01/9/2013
Overview
Execution After Redirect (EAR) is an attack where an attacker ignores redirects and retrieves sensitive content intended for authenticated users. A successful EAR exploit can lead to complete compromise of the application.
How to Test for EAR Vulnerabilities
Using most proxies it is possible to ignore redirects and display what is returned. In this test we use Burp Proxy.
- Intercept request https://vulnerablehost.com/managment_console
- Send to repeater.
- View response.
How to Prevent EAR Vulnerabilities
Proper termination should be performed after redirects. In a function a return should be performed. In other instances functions such as die() should be performed. This will tell the application to terminate regardless of if the page is redirected or not.
