Fix XSS vulnerability in HTML utility functions #9
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.
Currently, the HTML utility functions defined in
utils/html_utils.py
do not perform any escaping/sanitization on the strings passed to them before formatting the strings into the HTML to be returned.Jinja does not sanitize the strings either as the HTML returned by this function is stored in JSON and eventually rendered in-browser using JavaScript.
This results in a stored cross site scripting (XSS) vulnerability wherein a malicious user may upload a beatmap whose metadata values contain HTML and JavaScript and then add it to their playlist on osulist.
This change will escape all occurrences of
<
and>
characters in the input string, preventing the delineation of any HTML tags within it.