Potential fix for code scanning alert no. 24: Database query built from user-controlled sources #85
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/octodemo/vulnerable-node/security/code-scanning/24
To fix the problem, we need to use parameterized queries to safely embed user-provided data into the SQL query strings. This approach ensures that the user input is treated as a literal value and not as part of the SQL command, thus preventing SQL injection attacks.
We will modify the functions
getProduct,search,purchase, andget_purcharsedin themodel/products.jsfile to use parameterized queries provided by thepg-promiselibrary.Suggested fixes powered by Copilot Autofix. Review carefully before merging.