Resource amplification sink
What a resource-amplification finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-400.
Security explains how fallow finds it.
Why it matters
A size that comes from the request controls how much memory the code allocates. One request with a large value can exhaust the memory of the process.
Example
new Array(Number(req.query.count));
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 | resource-amplification |
| Rule id in SARIF output | security/resource-amplification |
| 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.