Case 73E2C7 · Web AppSec · L2 Practitioner

Mass Assignment

Practise as: Explain itLevel: L2 Practitioner
  1. 01 What is it?
  2. 02 How is it abused?
  3. 03 How do you stop it?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Frameworks bind request JSON straight onto model objects, so extra fields the UI never shows still get saved
  2. Abuse: add "role":"admin", "isVerified":true or "balance" to a profile update; read API docs or responses to find field names
  3. OWASP API Top 10 2023 groups it with excessive data exposure as API3, Broken Object Property Level Authorization
  4. Fix: explicit allowlists of writable fields per endpoint (DTOs, Rails strong parameters), never bind the raw entity
  5. Test by replaying requests with fields seen in GET responses; add schema validation that rejects unknown properties

If the interviewer pushes back

  • Why is a denylist of sensitive fields weaker than an allowlist as the model evolves?

Go deeper

More Web AppSec cards

All Web AppSec cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09