ascanrules: feat: Add specialized Blind SQL Injection Scanner #6543
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
- Implements dedicated BlindSqlInjectionScanRule for time-based and OAST detection - Addresses limitations of generic SQL injection scanner for blind scenarios - Supports 22 time-based payloads across MySQL, PostgreSQL, MS SQL, Oracle, SQLite - Includes 8 OAST payloads for out-of-band detection - Smart attack strength management (LOW: 3, MEDIUM: 8, HIGH: 15, INSANE: 22 payloads) - Proper integration with ZAP's TimingUtils and OAST framework - Comprehensive unit tests with 19 test cases covering all scenarios - Designed to detect vulnerabilities in apps like SasanLabs that return consistent responses This scanner complements the existing SQL injection scanner by specifically targeting blind SQL injection scenarios where boolean logic payloads fail but time-based and OAST attacks succeed.
|
Great job, no security vulnerabilities found in this Pull Request |
|
There's already some things planned around this and relevant to this:
|
- Changed plugin ID from 40029 to 40030 to avoid conflict with TraceAxdScanRule - Updated corresponding test assertion - All tests now passing (19 test cases) This resolves the CI build failures caused by duplicate plugin IDs.
- Reset CommandInjectionScanRule.java to original state from main branch - Reset CommandInjectionScanRuleUnitTest.java to original state from main branch - Keep only blind SQL injection scanner changes in this branch - Command injection enhancements should be in a separate PR
Your call :) |
This was referenced Jul 1, 2025
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.
This scanner complements the existing SQL injection scanner by specifically targeting blind SQL injection scenarios where boolean logic payloads fail but time-based and OAST attacks succeed.
Overview
Briefly describe the purpose, goals, and changes or improvements made in this pull request.
Related Issues
Specify any related issues or pull requests by linking to them.