Running the app on Docker

Reconnaissance

Step 1

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

Step 2

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 (Url. If we look at the code we discover a tiny difference: a blacklist!

If we look at the blacklist definition, we can immediately see that the URL, in order to be valid, must not contain any "." (dot).

Step 3

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.

Exploitation

Although we cannot explicitly use the dot character, we can find different ways to bypass the blacklist. For example we could use double encoding:

Using the payload above we will be able to successfully redirect a user to any website:

Additional sources

Running the app on Docker

Reconnaissance

Step 1

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

Step 2

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 (Url. If we look at the code we discover a tiny difference: a blacklist!

If we look at the blacklist definition, we can immediately see that the URL, in order to be valid, must not contain any "." (dot).

Step 3

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.

Exploitation

Although we cannot explicitly use the dot character, we can find different ways to bypass the blacklist. For example we could use double encoding:

Using the payload above we will be able to successfully redirect a user to any website:

Additional sources

Running the app on Docker

Reconnaissance

Step 1

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

Step 2

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-67-Url-redirection). If we look at the code we discover a tiny difference: a blacklist!

If we look at the blacklist definition, we can immediately see that the URL, in order to be valid, must not contain any "." (dot).

Step 3

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.

Exploitation

Although we cannot explicitly use the dot character, we can find different ways to bypass the blacklist. For example we could use double encoding:

Using the payload above we will be able to successfully redirect a user to any website:

Additional sources