Dangerous HTML sink
What a dangerous-html finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-79.
Security explains how fallow finds it.
Why it matters
If an attacker controls the value, the browser runs their script in the page (cross-site scripting). fallow does not prove that attacker input reaches the sink, so check the trace first.
Example
element.innerHTML = comment.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 | dangerous-html |
| Rule id in SARIF output | security/dangerous-html |
| 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.