Code injection sink
What a code-injection finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-94.
Security explains how fallow finds it.
Why it matters
The runtime executes the string as code. If an attacker controls it, they run code with the rights of the process. Check the trace before you fix.
Example
eval(req.body.expression);
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 | code-injection |
| Rule id in SARIF output | security/code-injection |
| 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.