Mass assignment sink
What a mass-assignment finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-915.
Security explains how fallow finds it.
Why it matters
All properties of the request object go into the target. An attacker can set fields that the form never shows, such as a role or an owner ID. Check the trace before you fix.
Example
Object.assign(user, req.body);
Fix
Review the candidate trace before acting. Confirm attacker control, missing sanitization, and reachable runtime context, then fix with the category-appropriate safer API or add a reviewed suppression.
Facts
| Fact | Value |
|---|---|
| Issue type | mass-assignment |
| Rule id in SARIF output | security/mass-assignment |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |
Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.