Open Redirect Vulnerability

Open redirect

Exploitation

Using a whitelisted domain or keyword

www.whitelisted.com.evil.com redirect to evil.com
https://www.target01.com//example.com/ redirect to //example.com/
https://www.target01.com%09.example.com redirect to example.com
https://www.target01.com%252e.example.com redirect to example.com

Using "//" to bypass "http" blacklisted keyword

//google.com

Using "https:" to bypass "//" blacklisted keyword

https:google.com

Using "//" to bypass "//" blacklisted keyword (Browsers see // as //)

\/\/google.com/
/\/google.com/

Using "/" to bypass:

/\google.com

Using "%E3%80%82" to bypass "." blacklisted character

Using null byte "%00" to bypass blacklist filter

Using parameter pollution

Using "@" character, browser will redirect to anything after the "@"

Creating folder as their domain

XSS from Open URL - If it's in a JS variable

XSS from data:// wrapper

Username

IP formats

You can also mix the different IP formats:

You can play with the different IP formats in https://www.silisoftware.com/tools/ipconverter.php

Parsing

Open Redirect to XSS

More domain bypasses

Open Redirect uploading svg files

Common injection parameters

Code examples

.Net

Java

PHP

Tools

Resources

In https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Open Redirect you can find fuzzing lists. https://pentester.land/cheatsheets/2018/11/02/open-redirect-cheatsheet.html https://github.com/cujanovic/Open-Redirect-Payloads

Last updated

Was this helpful?