Tainted sink candidates
What a tainted-sink finding of fallow security means, why it matters and how to fix it.
What it reports
Syntactic security sink candidates require verification.
Security explains how fallow finds it.
Why it matters
The tainted-sink family covers data-driven fallow security catalogue categories. These findings are unverified candidates, not confirmed vulnerabilities. fallow can connect known source signals to captured sink shapes and add CWE metadata, but it does not prove attacker control, missing sanitization, exploitability, or business impact.
Example
A non-literal request field reaches a catalogue sink such as security/sql-injection or security/dangerous-html. The finding is a candidate, not proof of exploitability.
Fix
Trace the source, sink, sanitization, and runtime context. Fix confirmed issues with parameterization, escaping, validation, or safer APIs, and suppress only reviewed false positives with context.
Facts
| Fact | Value |
|---|---|
| Issue type | tainted-sink |
| Rule id in SARIF output | security/tainted-sink |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |