Mass assignment leading to modification of account
The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by changing account value 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 be tested. It filters the endpoints based on the response code (between 200 and 299), the HTTP method (PUT, POST, or PATCH), and the presence of the "account" key in the response payload.
The template executes a single request by adding a body parameter to the request payload. It extracts the value of the "account_context" from the parameter context and adds it as a key-value pair in 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 "account_key" with a value equal to the "account_context.value".
Frequently asked questions
What is a Mass Assignment vulnerability and how does it impact the security of an application
How does the test identify if an API endpoint is vulnerable to Mass Assignment attacks
What are some examples of sensitive properties that should not be updated by clients
How does the test categorize the severity of a Mass Assignment vulnerability
What are the selection filters used to identify vulnerable API endpoints
How does the test validate if the vulnerability has been successfully exploited