Harden security: enable Jinja2 autoescape, add SQL table whitelist, enforce HTTPS#29
Merged
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
1 participant
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.
Hardens security across the codebase by closing three vectors identified during the codebase audit.
This PR enables Jinja2 autoescape on the HTML report template to prevent XSS from user-provided or dataset-sourced fields, adds a table name whitelist in load_data() to prevent SQL injection via interpolated table names, and enforces HTTPS in all API URL builders so that http:// hosts are upgraded rather than passed through with bearer tokens in cleartext.