Cookie dan sesi for GitLab
high5 checks
Session cookies are the keys to an account. Missing attributes turn a single XSS bug into full account takeover.
What GitLab must have
- Secure attribute on every cookie
- HttpOnly on session cookies
- SameSite=Lax or Strict on session cookies
- No session identifier in URLs or localStorage
- Session rotation after login and logout invalidation
How to fix it
- 1Set cookie attributes at the framework level so every cookie inherits them
- 2Move tokens out of localStorage to HttpOnly cookies
GitLab context
Self-hosted DevOps platform with git, CI and registries.
Password-reset account takeover (CVE-2023-7028) hit many self-hosted instances — keep it patched and behind SSO.