🙁
-UserInterface for this Vulnerability level is still in-progress.
-Please use API interface for learning/testing this vulnerability.
- -diff --git a/WebContent/static/error.css b/WebContent/static/error.css deleted file mode 100755 index dfd2b50..0000000 --- a/WebContent/static/error.css +++ /dev/null @@ -1,30 +0,0 @@ -#content { - - font-size: 18px; - font-weight: normal; - justify-content: center; - color: brown; -} - -.erroremoji -{ - font-size: 30px; - margin-bottom: 0px; - text-align: center; -} -.error-reason -{ - margin-top: 0px; - padding-top: 0px; - font-family: 'Secular One', sans-serif; - text-align: center; - -} - -.error-solution{ - color:dodgerblue; - font:bold; - text-align: center; - font-family: 'Secular One', sans-serif; -} - diff --git a/WebContent/static/error.html b/WebContent/static/error.html deleted file mode 100755 index c682dac..0000000 --- a/WebContent/static/error.html +++ /dev/null @@ -1,8 +0,0 @@ - - -
🙁
-UserInterface for this Vulnerability level is still in-progress.
-Please use API interface for learning/testing this vulnerability.
- -+ VulnerableApp-Facade was started when we were building{" "} + + File-upload addon + {" "} + for Owasp ZAP, which is used + to find the vulnerabilities in the File Upload functionality. As we + were developing the addon and writing the scan rules, in order to + test those scan rules we were using{" "} + + Owasp VulnerableApp + {" "} + but as Owasp VulnerableApp is written in Java and is a SpringBoot + application hence testing scan rules related to PHP, ASP, JSP etc + are not possible. Hence we thought of building a facade application + which acts as proxy or gateway to route the requests to vulnerable + applications written in different tech stacks. +
+
+
Following is the design diagram of Owasp VulnerableApp-Facade:
+ ++ Here VulnerableApp-Facade is running as a gateway or a proxy which + is routing calls to actual Vulnerable Applications based on a + criteria defined in nginx configuration. +
+