fix reverse tabnabbing attack possibility #10675
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
Reverse tabnabbing is an attack that is possible when a link is configured to open a new tab in a browser by, for example, adding the target="_blank" attribute to an tag. If done incorrectly, the new page is able to control the referrer and opener objects of the parent window, and use that control to replace the parent site with a phishing site.
To mitigate the possibility of Reverse Tabnabbing,
rel="noopener noreferrer"
needs to be added to<a>
tags.Issue #, if available
Description of how you validated changes
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.