Fix cookie set without its protective attributes in Fastify
A cookie is written without `httpOnly`, `secure`, or `sameSite`. Missing `httpOnly` turns any cross-site scripting bug into session theft; missing `secure` sends the cookie over plain HTTP; missing `sameSite` attaches it to cross-site requests. A cookie holding no sensitive value may not need all three, which is why the finding names the ones it did not find rather than assuming the worst.
medium likely Fastify CWE-614 / OWASP A05:2021
The vulnerable pattern in Fastify
This finding comes from the Fastify fixture in the owlwarden test suite. This cookie is missing protections: secure stops the cookie being sent over plain HTTP; sameSite stops the browser attaching the cookie to cross-site requests.
The corrected handler
Pass the attributes to reply.setCookie.
reply.setCookie('session', token, {
httpOnly: true,
secure: process.env.NODE_ENV === 'production',
sameSite: 'lax',
path: '/',
})If you are not using Fastify
Set httpOnly, secure, and sameSite when writing a cookie that carries anything the user would not want read or replayed.
Check your own repository
npx owlwarden scan
npx owlwarden explain insecure-cookieRuns on your machine. No account, no telemetry, no network unless you ask. In CI, SARIF uploads to code scanning and the exit code is the gate.
Other Fastify checks
Rules with a tested Fastify example.
- cors-permissive medium Cross-origin policy accepts any origin
- hardcoded-secret high Credential hardcoded in source
- install-lifecycle-script medium Package declares an install-time script
- open-redirect medium Redirect target comes from the caller
- security-headers-missing medium Security headers are not configured
- sensitive-data-logged medium Sensitive data written to a log
- sql-injection high SQL query built by string interpolation
- ssrf high Server fetches a URL the caller controls
- stack-trace-leak high Stack trace leaked in error response
- weak-crypto high Broken cryptographic primitive protecting a secret