Execution After Redirect (EAR)

Revision as of 10:56, 9 January 2013 by Robert Gilbert (talk | contribs) (Created page with "{{stub}} {{Template:Attack}} Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' ==Overview== Execution After Redirect (EAR) is an attack whe...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
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


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.

  1. Intercept request https://vulnerablehost.com/managment_console
  2. Sent to repeater.
  3. 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.