liveBook · Manning

Mass assignment

Mass assignment is the automatic binding of multiple client-supplied fields to an application's object or model properties, which can expose properties not intended for client modification.

How 2 Manning books explain it

Secure APIs

Mass assignment is an object-binding behavior that maps multiple client-supplied fields directly onto an application's object or model.

How it is used
Uses payment APIs to show how unrestricted field binding can let clients override business-critical state.
How deep it goes
Explains the failure mode, consequences, vulnerable and constrained implementations, but does not detail framework-specific internals.
Examples
Uses payment-status payloads, Ruby on Rails binding, and Python request schemas to demonstrate exploitation and prevention.
What you can do after
Diagnose unrestricted model binding and apply operation-specific request schemas that exclude server-controlled fields.

Read how Secure APIs explains mass assignment →

ASP.NET Core in Action, 3e

Overposting is a security vulnerability in which client-supplied fields are bound directly to properties that the application did not intend to expose for modification.

How it is used
Protects create and edit operations from unintended client-controlled property changes.
How deep it goes
Defines the vulnerability and demonstrates explicit mapping, but does not show a concrete attack payload.
Examples
Uses CreateRecipeCommand-to-Recipe mapping and a Razor Pages InputModel with selective property binding.
What you can do after
Apply it via purpose-specific binding models and explicit property mapping before persistence.

Read how ASP.NET Core in Action, 3e explains mass assignment →

Also covered in

What to know first

Related concepts

Questions about mass assignment

What is mass assignment?

Mass assignment is the automatic binding of multiple client-supplied fields to an application's object or model properties, which can expose properties not intended for client modification.

Which Manning books explain mass assignment?

Secure APIs and ASP.NET Core in Action, 3e.

What should I know before learning mass assignment?

Manning books that teach mass assignment usually introduce HTTP request first.

What is mass assignment part of?

Mass assignment is part of broken object property-level authorization. Broken object property-level authorization is an API vulnerability that fails to restrict access to object properties a requester should not read or modify.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.