@@ -39,7 +39,7 @@ https://user-images.githubusercontent.com/91306853/217300011-db834337-70d2-4985-
3939
4040https://user-images.githubusercontent.com/91306853/219386085-820ef832-3679-4d2c-9a7f-6af499923d21.mov
4141
42- ## Test 4 : Broken user authentication by removing auth token
42+ ## Test 4 : Swagger file detection - Security misconfiguration
4343
4444Step 1: Click on run and select swagger file detection test
4545Step 2: Go to testing and wait for a minute for test results
@@ -51,7 +51,11 @@ Step 6: Verify it by actually entering the URL
5151🐞 Detected unprotected swagger file!
5252
5353
54- ## Test 5 : Broken user authentication by removing auth token
54+ https://user-images.githubusercontent.com/91306853/221205469-12081044-f357-457c-a18e-0582dd4ba256.mp4
55+ 56+ 57+ 58+ ## Test 5 : JWT None algo attack
5559
5660Step 1: Look at the original data - last name is "johnson"
5761Step 2: Select the endpoint you want to test for JWT None attack
@@ -65,7 +69,11 @@ Step 8: Observe algo=none
6569🐞 JWT None algo vulnerability found
6670
6771
68- ## Test 6 : Broken user authentication by removing auth token
72+ https://user-images.githubusercontent.com/91306853/221205044-460ff9a1-7283-491e-9f6f-fc39a738c1e5.mp4
73+ 74+ 75+ 76+ ## Test 6 : JWT failed to verify signature test
6977
7078Step 1: Select a POST order endpoint
7179Step 2: Select the Broken Authentication test - JWT failed to verify signature
@@ -74,6 +82,12 @@ Step 4: Check the Original tab - the original token signature starts with "HQq0"
7482Step 5: Check Attempt tab - gives 200 OK response with signature starting with "aQq0" - this is invalid signature, yet server accepted
7583
7684
85+ 86+ https://user-images.githubusercontent.com/91306853/221205245-6c32c6d3-2863-4db7-aacf-fa0868f19970.mp4
87+ 88+ 89+ 90+ 7791## Test 7 : Broken user authentication by removing auth token
7892
7993Step 1: Select BOLA by parameter pollution
@@ -87,7 +101,7 @@ Step 7: The victim's cart has a new product added now!
87101🐞 Vulnerable API
88102
89103
90- ## Test 8 : Broken user authentication by removing auth token
104+ ## Test 8 : Broken Object Level Authorization in old API versions
91105
92106Step 1: Select the list of endpoints
93107Step 2: Select Old version API tests.
@@ -100,7 +114,11 @@ Step 7: Notice that /api/v1/users also returns 200 OK with the flag
100114🐞 BOLA in old api versions
101115
102116
103- ## Test 9 : Broken user authentication by removing auth token
117+ 118+ https://user-images.githubusercontent.com/91306853/221204869-5b191e29-9748-4e10-99e3-6c401569717f.mp4
119+ 120+ 121+ ## Test 9 : Security misconfiguration - django-exposed-debug-page
104122
105123Step 1: Select the Django-exposed-debug-page test and run it
106124Step 2: Wait for the result
@@ -111,7 +129,10 @@ Step 5: Observe we open the debug page - with details of modules, and inner work
111129🐞 django-exposed-debug-page
112130
113131
114- ## Test 10 : Broken user authentication by removing auth token
132+ https://user-images.githubusercontent.com/91306853/221204724-bb78be9a-378b-4456-a9f6-212b198f7893.mp4
133+ 134+ 135+ ## Test 10 : Security misconfiguration - Open redirects
115136
1161371 . Select the API Collection you want to test
1171382 . Select Open-redirect test under Security Misconfiguration and click on run test
@@ -122,3 +143,7 @@ Step 5: Observe we open the debug page - with details of modules, and inner work
1221437 . See the attempt succeeds! Server returns 302 with location evil. com.
123144
124145🐞 API is vulnerable!
146+ 147+ 148+ https://user-images.githubusercontent.com/91306853/221205729-97607d8d-6742-453f-a714-8b3985ccdc65.mp4
149+
0 commit comments