Further XSS fixes in link attrs (#703)#705
Open
Crozzers wants to merge 3 commits into
Open
Conversation
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
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.
Further fixes for #703, specifically the follow up issues raised in this comment: #703 (comment)
Issue 1:
For some reason html encoded colons function as normal colons in hrefs, so
javascript:alert()is equal tojavascript:alert().Fixed this by checking for these sequences alongside colons.
Issue 2:
The safe_href regex we use allows for URL domains with ports. This was intended for links like
localhost:880/abcdefbut could be abused by making the JS look like a domain with a port, like so:Issue 3:
This used some quirky markdown in a image title attr to escape the link. Fixed by hashing the title attr to prevent reprocessing, much like we do with
alt=