✨ (Sonar) Fixed finding: "Change this code to not construct SQL queries directly from user-controlled data." #37
+3
−6
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
…es directly from user-controlled data."
|
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.
✨✨✨
Remediation
This change fixes "Change this code to not construct SQL queries directly from user-controlled data." (id = javasecurity:S3649) identified by Sonar.
Details
SQL Injection is a security vulnerability that occurs when an application constructs SQL queries directly from user-controlled data, allowing attackers to manipulate the queries and potentially access or modify the database. The fix involves changing the SQL query construction to use parameterized queries instead of directly concatenating user-controlled data. This ensures that user input is properly escaped and prevents SQL injection attacks.