Tabnabbing via window.opener [bookwyrm.social] in bookwyrm-social/bookwyrm
Aug 5th 2022
- Hello @bookwyrm-social I found a tabnabbing vulnerability. attack is possible due to
taget=_blankor Tab nabbing via window.opener.
- I was browsing the site and found a tabnabbing vulnerability . As per the observation I found that attack is possible due to taget=_blank or Tab nabbing via window.opener. When you open a link in a new tab ( target="_blank" ), the page that opens in a new tab can access the initial tab and change it's location using the window.opener property.
STEPS TO REPRODUCE:
1- Open the website URL :-
2- Right-click and click on inspect element
3- Locate the cursor to Element Tab then do
CTRL+F or Search for taget="_blank"
4- If you get blank with a link it means website can be vulnerable like , open redirect like vulnerabilities
5- For More Details To Check the POC
POC Screenshot 1:
POC Screenshot 2:
In order to mitigate this issue, developers are encouraged to use rel="nofollow noopener noreferrer" as follows: <a target="_blank" class="btn external-url" href=#" https://evil.com " rel="nofollow noopener noreferrer"><i class="fa fa-external-link"></i> </a>
Don't open links in new tabs using the target="_blank" Add attribute rel="noreferrer" which also disables referrer Set the window.opener attribute to null on the new tab before redirecting, like this: <script>var w=window.open(url, "target=_blank");w.opener= null;</script>
External links in main domain :
- This type of Phishing has huge potential for tricking users that click on external links from this(your) website to be a victim of a scam page because the redirecting is made in the background, while the user is focused on another tab.
@maintainer are you happy to assign a CVE? please confirm, then only admin can move further
@admin can you pls assign a CVE for this?
@admin maintainer has requested a CVE via github
here is the link, check that:
So can we assign a CVE here?
Hey, in this case the maintainer has created and published security advisory only, the github staffs will verify this and assign CVE later(it may takes time accordingly), once the CVE is assigned by github, you can add the CVE number here and request admin for adding that to your profile
Okay @Akshay Ravi
Hi 👋 Once the CVE is added to the GitHub Security Advisory, we can add it to this report. Please let me know once it receives a CVE number :)
CVE-2022-35953 has assigned for this issue, can you please add this CVE on this report(CVE ID)
Sorted - the CVE has now been added to this report ♥️