|
9 | 9 |
|
10 | 10 | ## Steps to Perform This Attack :
|
11 | 11 | ```
|
12 |
| -Step 1 : Capture the request into Burp, Send the request to repeater and intruder tab |
13 |
| -Step 2 : Add the endpoint into the intruder tab and add the payload from the word-list |
14 |
| -Step 3 : 1st use dictionary attack with sec-list on the Endpoint |
15 |
| -Step 4 : Either use your customized list or use the ones which i have provided in the above section |
16 |
| -Step 5 : Then simply start the attack, Start checking for 200 status |
17 |
| -Step 7 : Once their is 200 status OK, Start the recursive scan on the same endpoint for juicy information like swagger doc and so on. |
| 12 | +Step 1 : Capture the request into Burp, Send the request to repeater and intruder tab. |
| 13 | +Step 2 : Add the endpoint into the intruder tab and add the payload from the word-list. |
| 14 | +Step 3 : First use dictionary attack with SecLists (https://github.com/danielmiessler/SecLists) on the Endpoint. |
| 15 | +Step 4 : Either use your customized list or use the ones which I have provided in the above step. |
| 16 | +Step 5 : Then simply start the attack, start checking for 200 status. |
| 17 | +Step 7 : Once there is HTTP 200 OK status, start the recursive scan on the same endpoint for juicy information like swagger doc and so on. |
18 | 18 | step 8 : Other method is to change the API version and try bruteforcing the same endpoint
|
19 | 19 | Eg: Redacted.com/api/v1/{Endpoint} ----- Redacted.com/api/v2/{Endpoint}
|
20 | 20 | ```
|
21 |
| -* Note: Their will be minimum limits per request which will be assigned without API keys so make sure to utilize manual approach as much as you can,Then the rest can be automated for scanning the vulnerability in API with automated tools. |
| 21 | +* Note: There will be minimum limits per request which will be assigned without API keys so make sure to utilize manual approach as much as you can, then the rest can be automated for scanning the vulnerability in API with automated tools. |
22 | 22 |
|
23 | 23 | ## Contributor:
|
24 | 24 | - [N3T_hunt3r](https://twitter.com/N3T_hunt3r)
|
0 commit comments