`insecure_cookie`

CWE-614

Insecure Cookie — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.

How to fix

Set HttpOnly + Secure + SameSite flags on session / auth cookies trivial effort

// Express
res.cookie("sid", token, { httpOnly: true, secure: true, sameSite: "lax" });

// Django settings.py (production)
SESSION_COOKIE_SECURE = True
SESSION_COOKIE_HTTPONLY = True
SESSION_COOKIE_SAMESITE = "Lax"

// Spring
CookieCsrfTokenRepository repo = CookieCsrfTokenRepository.withHttpOnlyFalse();
// (Spring session cookie is HttpOnly by default; don't call setUseHttpOnlyFlag(false))

// Rails
cookies.encrypted[:sid] = { value: token, httponly: true, secure: Rails.env.production? }

Triage

Suppress a confirmed non-issue with a committed .pullguardignore entry (pullguard ignore locally, or comment /pullguard ignore <fingerprint> <reason> on the PR — the fingerprint is printed in the PR comment’s Triage section). Entries support expiresAt for time-boxed snoozes.

Security findings at major or critical severity — and any critical finding — always surface: .pullguardignore cannot hide them. The reviewed paths that keep them visible are acknowledged (reviewed, stays in reports) and, for a confirmed false positive, a reasoned false_positive entry — visible and audited, excluded only from the merge block.