Fix Security Issues #542
Merged
Fix Security Issues #542
Conversation
This file contains 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
rutujaac
force-pushed
the
rutuja-fix-security-issues
branch
from
6b56bfd
to
b9006c0
Compare
Raj725
previously approved these changes
Sep 12, 2024
rutujaac
force-pushed
the
rutuja-fix-security-issues
branch
from
7699a4e
to
e9f4a58
Compare
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.
Addressed 3 issues of the following types:
Make sure that this dynamic injection or execution of code is safe: Refactored the filtering function on Applications List table and Snippets listing to prevent use of eval() in JS.
Make sure disabling auto-escaping feature is safe here: Added autoescape=jinja2.select_autoescape() to the Jinja2 Environment function to enable auto-escaping smartly for the given template file. All special characters would be rendered as strings.