01Description
Session cookies were set without one or more of the Secure, HttpOnly and SameSite attributes.
02Impact
Without Secure, cookies may be sent over unencrypted connections. Without HttpOnly, script injected through cross-site scripting can read the session cookie. Without SameSite, cookies are sent with cross-site requests, increasing exposure to cross-site request forgery.
03Severity
Typically
Low
Typically Low. Low on its own. Raise to Medium if a cross-site scripting or cleartext exposure was also found, as missing flags make session theft straightforward.
04How to verify
- 1Inspect Set-Cookie headers after authentication.
- 2Record the attributes on each session and authentication cookie.
- 3Confirm which cookies are used for session management.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Set Secure and HttpOnly on all session and authentication cookies.
- 2Set SameSite=Lax or Strict as appropriate for the application's flows.
- 3Consider the __Host- cookie prefix for session cookies.
Draft findings like this from your own evidence
Book a demo