Fix code scanning alert no. 3: SQL query built from user-controlled sources #1
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/github-cloudlabsuser-128/ghas-bootcamp-python/security/code-scanning/3
To fix the SQL injection vulnerability, we should use parameterized queries instead of directly embedding user input into the SQL query string. Parameterized queries ensure that user input is properly escaped and treated as data rather than executable code.
In this specific case, we will modify the
cursor.execute
call on line 23 to use a parameterized query. This involves replacing the f-string with a query that uses placeholders for parameters and passing the user input as a separate argument to theexecute
method.Suggested fixes powered by Copilot Autofix. Review carefully before merging.