How to fix: document.cookie write missing Secure flag
Cookies set via document.cookie without Secure can be sent over HTTP.
Why it matters
Add Secure; to every cookie set via document.cookie
Cookies set via document.cookie without Secure can be sent over HTTP.
How to fix it
- 1Add Secure; to every cookie set via document.cookie
Code examples
Set the Secure flag on all cookies
res.setHeader("Set-Cookie",
`session=${token}; HttpOnly; Secure; SameSite=Strict; Path=/`
);
// Secure: cookie is only sent over HTTPS connections
// Without Secure, cookie can be stolen over HTTP (SSL-stripping attack)References
Detected automatically by VulnRadar. The check id is code-cookie-write-no-secure, 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 document.cookie write missing Secure flag?
- 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-write-no-secure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does document.cookie write missing Secure flag 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.