NodeJS - URL Redirection - Harder
$ sudo docker pull blabla1337/owasp-skf-lab:js-url-redirection-harder
$ sudo docker run -ti -p 127.0.0.1:5000:5000 blabla1337/owasp-skf-lab:js-url-redirection-harder
Now that the app is running let's go hacking!
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.
Intercepting the traffic generated by the application, we note that the redirection is performed using the following call
GET /redirect?newurl=newsite
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!
let newurl = req.query.newurl;
if (blacklist(newurl)) {
res.render("index.ejs", {
content: 'Sorry, you cannot use "." in the redirect',
});
If we look at the blacklist definition, we can immediately see that the URL, in order to be valid, must not contain any "." (dot).
const blacklist = (newurl) => {
if (newurl.includes(".")) {
return true;
}
return 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. For example we could use double encoding:
https://www%252egoogle%252ecom
Using the payload above we will be able to successfully redirect a user to any website:
Last modified 8mo ago