Fix XSS issue in safe mode (#601)#602
Merged
Merged
Conversation
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes #601 by making the HTML tokenisation regex more lenient.
Currently, the regex matches HTML tags and their attributes, using
[\w-]for the attribute name. However, in the HTML spec it says:The current character class being used does not include all these possibilities so I've updated it to instead exclude these banned characters:
[^<>"'=/].I also tweaked how the attribute values are matched. The current regex only allows for quoted values, which lets
src=# onerror=alert()slip past. I've added another clause in the regex that matches unquoted attr values as long as they don't contain a space (because that would count as the next attribute)