Fix code scanning alert no. 9: Database query built from user-controlled sources #589
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/sipcapture/homer-app/security/code-scanning/9
To fix the problem, we should ensure that user-provided values are safely embedded into the SQL query using parameterized queries. GORM already provides a way to safely handle user input by using maps in the
Where
method. However, we should explicitly use parameterized queries to ensure that the values are properly escaped.We will modify the
Get
,Delete
, andUpdate
methods in theUserSettingsService
to use parameterized queries with named placeholders. This will ensure that the user-provided values are safely embedded into the SQL query.Suggested fixes powered by Copilot Autofix. Review carefully before merging.