Version 1.2 and forward of the OWASP Benchmark for Java is a fully executable web application, which means it is scannable by any kind of vulnerability detection tool. v1.2 has been limited to slightly less than 3,000 test cases, to make it easier for DAST tools to scan it (so it doesn’t take so long and they don’t run out of memory, or blow up the size of their database). The 1.2 release covers the same vulnerability areas that 1.1 covers. The bulk of the work was turning each test case into something that actually runs correctly and is fully exploitable, and then generating a UI on top that works in order to turn the test cases into a real running application. The test case areas and quantities for the OWASP Benchmark for Java releases are: Vulnerability Area|# of Tests in v1.1|# of Tests in v1.2|CWE Number Command Injection|2708|251|78 Weak Cryptography|1440|246|327 Weak Hashing|1421|236|328 LDAP Injection|736|59|90 Path Traversal|2630|268|22 Secure Cookie Flag|416|67|614 SQL Injection|3529|504|89 Trust Boundary Violation|725|126|501 Weak Randomness|3640|493|330 XPATH Injection|347|35|643 XSS (Cross-Site Scripting)|3449|455|79 Total Test Cases|21,041|2,740| Each Benchmark version comes with a spreadsheet that lists every test case, the vulnerability category, the CWE number, and the expected result (true finding/false positive). Look for the file: expectedresults-VERSION#.csv in the project root directory. Every test case is: