Cookie dan sesi for Tomcat
high5 checks
Session cookies are the keys to an account. Missing attributes turn a single XSS bug into full account takeover.
What Tomcat 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
Tomcat context
Java servlet container / application server.
Never publish /manager or /host-manager. Partial PUT handling was RCE (CVE-2025-24813).