Skip to content
StrikeOps

Mass Assignment

HighTypical severity Web applications and APIsCWE-915

01Description

The API bound all fields supplied in a request directly to internal data objects, allowing clients to set fields they should not control.

02Impact

An attacker can modify fields such as their role, verification status, tenant or price by adding them to a request, leading to privilege escalation or fraud.

03Severity

Typically

High

Typically High. High where users can set privileged fields such as role, account owner or balance. Medium where only non-sensitive fields are affected.

04How to verify

  1. 1Compare fields returned by the API with fields accepted on create and update requests.
  2. 2Add privileged fields such as isAdmin, role or tenantId to requests from a low-privileged test account.
  3. 3Confirm whether the values were stored.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Accept only an explicit allow-list of fields for each operation, using separate input models.
  2. 2Never bind request bodies directly to database models.
  3. 3Enforce authorization on sensitive field changes server-side.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo