[A1][Mitigation] Use prepared statement to avoid injection in SQL queries. #29
Conversation
This file contains 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
spimpaov
approved these changes
Jan 8, 2019
There was a problem hiding this comment.
Nice job! Your solution mitigates SQL Injection from the application.
If you want to go even further, consider using db.Prepare function too to potentially improve the performance of the queries that need to be executed often.
|
@Chavao , sounds good to me as well! Awesome! On future commits we will mention this PR as a mitigation solution! 🔒 |
rafaveira3
added
mitigation solution 🔒
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.
Running
sqlmapwith command:sqlmap -r postRequest.txtThe output is:
all tested parameters do not appear to be injectable.Full output file
sqlmap_output.txt.