Skip to content
Fallow home
All docs pages

Docs home

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

FactValue
Issue typeinsecure-cookie
Rule id in SARIF outputsecurity/insecure-cookie
Commandfallow security
Default severityoff
Suppression comment// fallow-ignore-next-line security-sink
Fixable with fallow fixNo
Opt-inYes

Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.