Description
The absence of the Secure flag in cookies allows them to be transmitted over unencrypted connections, making them vulnerable to interception by attackers conducting man-in-the-middle (MitM) attacks. A cookie with the Secure flag is only sent to the server with encrypted requests over HTTPS, ensuring its confidentiality and integrity.
Recommendation
To enhance security, always set the Secure flag for cookies, especially for those containing sensitive information such as session tokens or user credentials. This ensures that the cookies are only transmitted over secure, encrypted connections, mitigating the risk of interception by attackers.
References
Could your website be exposed too?
SmartScanner can check your website for Cookie without Secure Flag and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Session Cookie without Secure Flag - Vulnerability
- Session Cookie without SameSite Flag - Vulnerability
- Session Cookie without HttpOnly Flag - Vulnerability
- Cookie without HttpOnly Flag - Vulnerability


