$ docker pull blabla1337/owasp-skf-lab:url-redirection-harder2
$ docker run -ti -p 127.0.0.1:5000:5000 blabla1337/owasp-skf-lab:url-redirection-harder2
First, make sure python3 and pip are installed on your host machine. After installation, we go to the folder of the lab we want to practise "i.e /skf-labs/XSS/, /skf-labs/jwt-secret/ " and run the following commands:
$ pip3 install -r requirements.txt
$ python3 <labname>
The application shows that there is a new version of the website available somewhere, and a click on the button "Go to new website" will redirect you to it.
If we click on the button we will be redirected on the new page http://localhost:5000/newsite
Intercepting the traffic generated by the application, we note that the redirection is performed using the following call
that will generate a 302 Redirect response from the server
Exactly like in the previous example (KBID XXX). If we look at the code we discover a tiny difference: a blacklist!
landing_page = request.args.get('newurl')if blacklist(landing_page):return render_template("index.html", content = "Sorry, you cannot use \".\" and \"/\" in the redirect. Good luck!")return redirect(landing_page, 302)
If we look at the blacklist definition, we can immediately see that the URL, in order to be valid, must not contain any "." (dot) and "/\" (forward slash).
def blacklist(url):blacklist = [".","/"]for b in blacklist:if url.find(b) != -1:return Truereturn False
Let's verify the effectiveness of this blacklist. If we try to exploit the unvalidated redirect using an external website, we see that the application blocks us, returning an error in the page.
If we URL encode the dot the application is smart enough to decode it and recognise it in the URL, blocking us again.
Although we cannot explicitly use the dot character, we can find different ways to bypass the blacklist. In example we could use the following techniques:
Can you find more?
The "." (dot) blacklist bypass is done, now it's time of "\/" (forward slash).
Double encoding won't work on this case because the browser doesn't understand the URL redirection of duble encoded "/\".
With HTTPS protocol, the "\/" can be omitted. The browser will understand this URL and fix the "mistake" and will add the missing protocol double forward slashes.
Therefore, the final payload is:
Can you find more ways to bypass "\/" blacklist validation?
Using the payload above we will be able to successfully redirect a user to a malicious website