Fix code scanning alert no. 21: Uncontrolled data used in path expression #78
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
…sion Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
Fixes https://github.com/google/litmus/security/code-scanning/21
To fix the problem, we need to ensure that the
filenameparameter is sanitized and validated before it is used to construct thetemp_filename. We can use thewerkzeug.utils.secure_filenamefunction to sanitize the filename, ensuring it does not contain any special characters or path traversal sequences. Additionally, we should normalize the path to ensure it stays within the intended directory.secure_filenamefunction fromwerkzeug.utils.secure_filenameto sanitize thefilenameparameter.temp_filenameusing the sanitized filename.Suggested fixes powered by Copilot Autofix. Review carefully before merging.