Insecure cookie options
What an insecure-cookie finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-614.
Security explains how fallow finds it.
Why it matters
Without httpOnly, a script in the page can read the cookie. Without secure, the browser also sends it over plain HTTP, where others on the network can read it.
Example
res.cookie('session', id, { httpOnly: false });
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 | insecure-cookie |
| Rule id in SARIF output | security/insecure-cookie |
| 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.