fix(sqli-blind): use prepared statements to prevent blind SQL injection (CWE-89) - #269
Open
markuszaki wants to merge 1 commit into
Open
markuszaki wants to merge 1 commit into
markuszaki wants to merge 1 commit into
Conversation
🏆 DVWA — CTF Patch Score2 / 55 challenges patched
Commit: 🎉 Your result is on the leaderboard — see where you rank! 🏆 |
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
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.
Blind SQL Injection Fix
Vulnerability: CWE-89 - SQL Injection (Blind)
OWASP Top 10: A03:2021 - Injection
Challenges Fixed: 3 (Low, Medium, High)
Issue
Blind SQL injection allowed attackers to extract data through boolean/time-based inference.
Fix
All three security levels now use:
Files Changed
Security Pattern: Prepared statements + generic responses
Verification: Patterns validated via ad-hoc script ✓