Unsafe deserialization sink
What an unsafe-deserialization finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-502.
Security explains how fallow finds it.
Why it matters
The parser can create objects or run code from the input. An attacker who controls the input can then run code in the process. Check the trace before you fix.
Example
yaml.load(req.body.config);
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 | unsafe-deserialization |
| Rule id in SARIF output | security/unsafe-deserialization |
| 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.