ZAP vs Wavsep

WAVSEP is a vulnerable web application designed to help assessing the features, quality and accuracy of web application vulnerability scanners.

It is the most comprehensive OSS DAST specific test suite that we know of.

This version of WAVSEP is now maintained by the ZAP Team: https://github.com/zaproxy/wavsep

Click on the Sections to see the full set of results, which also give the local URL and the scan rule which should find the vulnerability.

⚠️ Warning

We are still in the process of configuring and checking this scan, so you should not rely on the results just yet.

We are also aware that some tests are broken - they are shown as “⚠️ Broken” and do not count as failures.

Section Score
Total
96%
DOM XSS GET Experimental
100%
Local File Include GET 200 Error
100%
Local File Include GET 200 Identical
100%
Local File Include GET 200 Valid
100%
Local File Include GET 302 Redirect
100%
Local File Include GET 404 Error
100%
Local File Include GET 500 Error
100%
Local File Include GET False Positives
75%
Local File Include POST 200 Error
100%
Local File Include POST 200 Identical
100%
Local File Include POST 200 Valid
100%
Local File Include POST 302 Redirect
100%
Local File Include POST 404 Error
100%
Local File Include POST 500 Error
100%
Remote File Include GET 200 Error
100%
Remote File Include GET 200 Identical
100%
Remote File Include GET 200 Valid
100%
Remote File Include GET 302 Redirect
100%
Remote File Include GET 404 Error
100%
Remote File Include GET 500 Error
100%
Remote File Include GET False Positives
100%
Remote File Include POST 200 Error
100%
Remote File Include POST 200 Identical
100%
Remote File Include POST 200 Valid
100%
Remote File Include POST 302 Redirect
100%
Remote File Include POST 404 Error
100%
Remote File Include POST 500 Error
100%
Reflected XSS Cookie Experimental
0%
Reflected XSS GET
84%
Reflected XSS GET Experimental
9%
Reflected XSS POST
84%
Reflected XSS POST Experimental
75%
Reflected XSS GET False Positives
100%
SQL Injection GET 200 Error
100%
SQL Injection GET 200 Error Experimental
100%
SQL Injection GET 200 Identical
38%
SQL Injection GET 200 Valid
95%
SQL Injection GET 500 Error
100%
SQL Injection POST 200 Error
100%
SQL Injection POST 200 Error Experimental
100%
SQL Injection POST 200 Identical
38%
SQL Injection POST 200 Valid
95%
SQL Injection POST 500 Error
100%
SQL Injection GET False Positives
70%
Unvalidated Redirect GET 200 Valid
100%
Unvalidated Redirect GET 200
100%
Unvalidated Redirect GET False Positives
78%
Unvalidated Redirect POST 200 Valid
100%
Unvalidated Redirect POST 302
100%

 

Configuration

Config Details
Frequency Manual
Scripts https://github.com/zapbot/zap-mgmt-scripts/blob/master/scans/wavsep
Action https://github.com/zapbot/zap-mgmt-scripts/actions/workflows/zap-vs-wavsep.yml

 

Settings

All of the relevant rules were run at HIGH strength, with the exception of Path Traversal which is run at insane. However because we are excluding the Windows technology, the Path Traversal rule actually makes the same number of requests that it would do at High with no technology excluded.