Fix code scanning alert no. 1: SQL query built from user-controlled sources #2
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
…ources Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
yets |
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.
Fixes https://github.com/fba223/demo-python/security/code-scanning/1
To fix the SQL injection vulnerability, we should use parameterized queries. This approach ensures that user input is properly escaped and treated as data rather than executable code.
In the provided code, we need to modify the SQL queries on lines 16 and 22 to use parameterized queries. This can be done by using placeholders (
%s) in the SQL string and passing the user-provided values as parameters to thecursor.executemethod.Suggested fixes powered by Copilot Autofix. Review carefully before merging.