Reverse Tabnabbing or also known as Unsafe Target Blank is one of the most underrated vulnerability, and this is the one I like the most. It’s really easy to find an exploitable web application and it’s also quite easy to mitigate.
So what is Reverse Tabnabbing?
window.referrer just stores the website that opened the page.
window.opener has a reference to the page that opened the new one.
Nowadays browsers prevent the access to most of the properties of this variable, since it posed many security risks, but there are still some properties that you can access/change, being the most important window.opener.location.
Note that you cannot read window.opener.location, but you can change its value. If you need to get the url from where the user came from you can use document.referrer
Lets work with the following code which contains a unsafe target blank implementation:
You can find the code and try it here
Now if a victim opens this link, the ‘malicious’ page can see where the user came from and even redirect him
This is the malicious code:
If you test the above example and open the link, you will see that your previous tab gets redirected to google.
What can an attacker do?
A malicious page can first, get the page where you came from, lets say facebook. Then it redirects your other tab to a facebook phishing page. Just exactly like facebook, but you are not logged in. Maybe you could find it weird, and try to understand what is the problem, why you were logged out, but most of the users would just ignore it, as they ignore invalid SSL warnings, and try to log in. At this point an attackers gets the credentials you typed in, and game over.
Another thing that can be done, is for websites to monitor from which page you came from, and build a profile for you, the sites you visit, and consequently your interests. This is awesome for targeted advertising for example.
How to Protect it
The protection is quite easy. You just need to add to your link the rel attribute like so:
This will ensure the new page will not have the window.opener nor window.referrer properties.
You can test the prevention here