How to fix: Cookie written without Secure flag on HTTP
document.cookie = 'sid=' + token without '; Secure' allows the cookie to be transmitted over HTTP. Network observers and downgrade attackers can read or replay it.
Why it matters
Cookie captured on an unencrypted hop enables session hijacking without ever breaking TLS at the user.
The `code-cookie-missing-secure-http` check verifies that the server does not expose the `cookie-missing-secure-http` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Append '; Secure' to every document.cookie write for sensitive values.
- 2Better: set the cookie from the server via Set-Cookie with Secure; HttpOnly; SameSite.
- 3Add HSTS so the browser refuses plain-HTTP requests for the host.
Code examples
Always set Secure flag on cookies
// Without Secure, cookies are sent over HTTP connections
// making them vulnerable to interception on the network
res.setHeader("Set-Cookie",
`session=${token}; HttpOnly; Secure; SameSite=Strict; Path=/; Max-Age=3600`
);
// In development (HTTP), you may need to omit Secure, use NODE_ENV check:
const secure = process.env.NODE_ENV === "production" ? "; Secure" : "";
res.setHeader("Set-Cookie", `session=${token}; HttpOnly${secure}; SameSite=Strict; Path=/`);References
Detected automatically by VulnRadar. The check id is code-cookie-missing-secure-http, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Cookie written without Secure flag on HTTP?
- VulnRadar rates this medium severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-cookie-missing-secure-http, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Cookie written without Secure flag on HTTP map to?
- It maps to CWE-614. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.