These docs are for v1.1. Click to read the latest docs for v1.2.

Mass Assignment

Severity: Medium
Test name: Mass Assignment
Summary
Summary

Some software frameworks support the Massive Assignment feature. This is a convenient way of populating an entity with user inputs using a single line of code. It populates the attributes of the entity by assigning the input data directly to the corresponding properties.
Mass Assignment vulnerability allows an attacker to modify object properties, which are not supposed to be changed by the user, by assigning user input data (for example, JSON) without proper validation.

Impact

This vulnerability may lead to:

  • Privilege escalation. The attacker is able to change permission related properties
  • Data tampering by changing process related properties (for example, total price)
  • Bypass of security mechanisms
Example (privilege escalation)
  1. The source code of User entity in the application:

    <?php
    class User 
    {
        private string $email;
        private string $role;
    
        // Getter & setter 
        ...
    }
    
  2. The request which changes the user's email:

PUT https://www.{your_web_site}.com/api/user/{user_id}
{"email": "[email protected]"}
  1. The attacker fulfills the request with the following payload:
{"email": "[email protected]", "role": "SuperAdmin"}
  1. If an API request is vulnerable to mass assignment, the attacker gets the Super Admin privilege.
Location

The issue can be found in the source code on the server side.

Remedy suggestions
  • Avoid mass assignment data in your application if possible (avoid using functions that automatically bind a client’s input into code variables or internal objects). Instead of that, assign data for each property separately.
  • Specify a whitelist of attributes / properties (safe attributes / properties) which can be modified by a client.
  • Specify a blacklist of attributes / properties which cannot be modified by a client.
  • Validate values for each attribute which is used in mass assignment. Explicitly define and enforce schemas for the input data payloads.
Classifications
  • CWE-915
  • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
References