Trim user input before sending to detectSqlInjection#291
Open
bitterpanda63 wants to merge 2 commits into
Open
Conversation
After adding .strip to user input normalization, inputs like "\n123\n" are reduced to "123" which is correctly considered safe (alphanumeric). This is consistent with " 123 " (spaces) already being a refute_attack case.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Strips leading/trailing whitespace from user input before SQL injection detection, matching the fix applied to the Java firewall in AikidoSec/firewall-java#298.
Problem: An attacker can pad their payload with trailing whitespace (e.g.
"payload "). If the DB driver trims this before execution, the SQL query won't contain the padded input, causing@query.include?(@input)to return false (missed detection).Fix: Apply
.downcase.stripto the user input in the SQLInjectionScanner initializer.See: AikidoSec/firewall-java#298
Summary by Aikido
🐛 Bugfixes
More info