Mass assignment leading to creation of admin role
The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by adding role with admin permissions in request body. The application responded with 2XX success code in response.
Mass Assignment (MA)
How this template works
The template uses API selection filters to specify the criteria for selecting the API endpoints to test. It filters the endpoints based on the response code (between 200 and 299), the HTTP method (PUT, POST, or PATCH), and the URL containing the word "user". It also checks if the request payload contains either the "email" or "login" key, and if the response payload contains the "role" key.
The template executes a single request by adding a body parameter to the request. In this case, it adds the "role" parameter with the value "admin" to the request body.
The template validates the response by checking if the response code is between 200 and 299, and if the response payload contains the string "admin". If both conditions are met, the validation is considered successful.
Frequently asked questions
What is the purpose of the "Mass Assignment Create Admin Role" test
How does the test determine if the API endpoint is vulnerable
What are the potential impacts of exploiting this vulnerability
What are some examples of sensitive properties that should not be updated by the client
What are the recommended references for understanding Mass Assignment vulnerabilities
What are the selection filters used to identify the API endpoints for this test