-
Notifications
You must be signed in to change notification settings - Fork 105
Installation
Yalçın YOLALAN edited this page Apr 4, 2018
·
8 revisions
C#
Microsoft Visual Studio Community Edition 2017 (https://www.visualstudio.com/downloads/)
Windows OS (7 or later)
.Net Framework 4.7 (https://www.microsoft.com/en-us/download/details.aspx?id=55170)
Step 1: Download the WSSAT folder and copy/extract it to your Windows computer
Step 2: Go to WSSAT WSSAT\WSSAT\bin\Debug folder (Read/Write permission is required to generate report, log etc.)
Step 3: Double click WSSAT.exe
Step 1: Create Web Site for WSSAT\WebService2Test folder on IIS
Step 2: Create Web Site for WSSAT\WSAPI2Test folder on IIS
Step 3: Create MSSQL database TESTDB
Step 4: Create table Users with following fields:
[Id] [int] IDENTITY(1,1) NOT NULL,
[UserName] [nvarchar](50) NOT NULL,
[Password] [nvarchar](50) NOT NULL,
[Name] [nvarchar](50) NOT NULL,
DB Table Creation Script: https://github.com/YalcinYolalan/WSSAT/blob/master/WebService2Test/Sqli-test-table-creation-script.sql
Step 5: Enter database connection information in WSSAT\WebService2Test\Web.config and WSSAT\WSAPI2Test\Web.config
Step 6: Test it http://[your_site_name_1]/Sqli.asmx?WSDL and http://[your_site_name_2]/api/xss?txt=<script>alert(1)</script>
- Home
- Installation
- Usage
- Default Parameter Values
- Scope
- Donation
-
Testing Activities
- XML Bombs
- External Entity Attacks
- Insecure Communication
- Insufficient Authentication Test
- Cross Site Scripting
- SQL Injection
- XPATH Injection
- Verbose SOAP Fault Message
- Weak WS-SecurityPolicy: Insecure Transport
- Weak WS-SecurityPolicy: Insufficient Supporting Token Protection
- Weak WS-SecurityPolicy: Tokens Not Protected
- Weak XML Schema: Undefined Namespace
- Weak XML Schema: Unbounded Occurrences