A1:2021 | Insecure Direct Object Reference (5) | Cycubix Docs

Playing with the Patterns

1) View Another Profile

View someone else’s profile by using the alternate path you already used to view your own profile. Use the 'View Profile' button and intercept/modify the request to view another profile. Alternatively, you may also just be able to use a manual GET request with your browser.

Before finding the solution, it is crucial to highlight that this lesson's solution is connected to the solutions for IDOR 1, 2, 3, and 4. If you are resuming this exercise after some time, please refresh the results of the previous lessons to ensure continuity.

Perform actions within the IDOR lesson to generate HTTP requests. For example, viewing a user profile that includes a user ID in the URL.
We can use ZAP, Burp or developer tools to capture these requests and note the structure of the URLs and parameters.
We need to find the user ID. For this we can either send the request to the FUZZER (equal to the Intruder in Burp Suite), or predict the value through the browser.

a) Predicting the Value through the browser

You will see the following result

Now, try with different numbers. For example profile/2342385/2342386/2342387/2342388.

We can see that the correct profile corresponds to 2342388.

b) Predicting the value through ZAP Fuzzer

Go into the capture request corresponding to userID 2342384. Right click on it and select "Attack/Fuzz".

Highlight the userID and then select "Add" to select the Payload. Click again Add and select the option Numberzz. You can now select the range of numbers you want to look at, for example for 2342380 to 2342390. You can generate a preview and then select Add.
Start the Fuzzer. Select the payload you want to look at and Open the Request Editor (equivalent to the Repeater on Burp Suite). Click on "SEND" and see the Response.

c) Predicting the value with BURP.

Turn on the interceptor in Burp Suite.
Press view profile in WebGoat.
See the request on BurpSuite HTTP History.

Send the request to Intruder.

Press "clear" on the top right button. Change the URL to "/WebGoat/IDOR/profile/userId", and add "userId" in the Payload. "userId" should be replaced with the one just queried.

Open payloads tab and sumbit a range of numbers for "userId".

Start the attack. Find the correct response for "UserId".

2) Edit Another Profile

Older apps may follow different patterns, but RESTful apps (which is what’s going on here) often just change methods (and include a body or not) to perform different functions.
Use that knowledge to take the same base request, change its method, path and body (payload) to modify another user’s (Buffalo Bill’s) profile.
Change the role to something lower (since higher privilege roles and users are ususally lower numbers). Also change the user’s color to 'red'.

Solution with ZAP

Go to the section WEBGOAT/IDOR Edit another profile and hit the View Profile Button.
Find the request on ZAP and send it to the manual Request Editor.

Change the Method from GET to PUT. Then place edit the userID placing 2342388.
Change content type for the following:
```
application/json; charset=UTF-8
```
In Content lenght put 47 and the following content:

Click send and you should see the following Response:

Solution with BURP

The default request here won't work at all, so you will need to manually craft the request or tamper it with a proxy. To edit the other user's profile, you will use the same Url you did to view the other user's profile.
In order to change the request, send to the Repeater Buffalo Bill's payload. Then proceed to change the request manually. Change GET for PUT and content type change it to "application/json".

In the last line, change the request by adding the following parameters "role: 0, color: red, size: large, name: Buffalo Bill, userId: 234238".

Why did we change GET for PUT? Which are the RESTful methods used for "update" or "edit"?: