| Scanner | Version | Vendor |
| SQLiX | 1.0 | OWASP |
| Tested Against WAVSEP Version: |
| Detection Accuracy | Chart | ||||
| 37.50% Detection Rate 20.00% False Positives | (51/136) (2/10) |
| Response Type | Input Vector | Detection Rate | Details |
| Errorneous 500 Responses | HTTP GET (Query String Parameters) | 20 out of 20 | Cases Detected: 1(1st&2nd)-19 |
| Errorneous 500 Responses | HTTP POST (Body Parameters) | 0 out of 20 | Cases Missed: 1(1st&2nd)-19 |
| Errorneous 200 Responses | HTTP GET (Query String Parameters) | 20 out of 20 | Cases Detected: 1(1st&2nd)-19 |
| Errorneous 200 Responses | HTTP POST (Body Parameters) | 0 out of 20 | Cases Missed: 1(1st&2nd)-19 |
| Valid 200 Responses | HTTP GET (Query String Parameters) | 8 out of 20 | Cases Detected: 2,6,7,11-13,16,17 Cases Missed: 1(1st&2nd),3-5,8-10,14,15,18,19 |
| Valid 200 Responses | HTTP POST (Body Parameters) | 0 out of 20 | Cases Missed: 1(1st&2nd)-19 |
| Identical 200 Responses | HTTP GET (Query String Parameters) | 3 out of 8 | Cases Detected: 1-3 Cases Missed: 4-8 |
| Identical 200 Responses | HTTP POST (Body Parameters) | 0 out of 8 | Cases Missed: 1-8 |
| False Positive SQLi Test Cases | HTTP GET (Query String Parameters) | 2 out of 10 | Case 8 (warning), RXSS false positive cases 1,3,6,7 (represented as an addition of 1) |
| The tool wasn?t able to the scan the application when directed to a specific file name, so I had to copy the content of the internal index page (index-sql, index-false) to the index.jsp file (it solves the problem) and initiate the scan in front of the application?s root directory.
The scan was eventually executed with the following command: Perl SQLiX.pl -crawl http://192.168.1.100:8080/wavsep/ -all ?v=2 The tool didn?t manage to scan the false positive case ?7?, and crashed every time it did (so I simply removed the link from the directory index page before completing the scan). |