Potential fix for code scanning alert no. 2: 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.
Potential fix for https://github.com/jonath92/demo-python/security/code-scanning/2
To fix the problem, we need to use parameterized queries instead of directly concatenating user input into the SQL query. Parameterized queries ensure that user input is properly escaped and treated as data rather than executable code, thus preventing SQL injection attacks.
The best way to fix the problem without changing existing functionality is to modify the
cursor.execute
calls to use placeholders for user input and pass the user-provided values as parameters. This change should be applied to both thename
andauthor
parameters.Suggested fixes powered by Copilot Autofix. Review carefully before merging.