Secure Authentication and Session Management in Java EE
summary
Java EE does not secure authentication and sessions automatically; live demos exploit session IDs in URLs, network-sniffed cookies and XSS to hijack accounts. Tools shown include TCPdump and Cookie Manager and a tiny servlet that logs stolen cookies; attacks successfully replay sessions and perform CSRF money transfers. Fixes demonstrated are setting tracking mode to cookie, enabling HttpOnly and secure flags, serving static assets separately, and calling changeSessionId (Java EE 7) after login; recommended timeouts: 2–5 minutes for critical apps, 15–30 otherwise.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 1:34Security problems and HTTP sessions
- 7:14Demo: Session hijacking via URL
- 12:47Demo: Session hijacking via network sniffing
- 16:55Securing session IDs during transport
- 21:00Demo: Cross-site scripting attack
- 26:16Preventing XSS with HTTP-only cookies
- 28:30Session fixation and ID rotation
- 31:49Enhancing session security with fingerprints
- 33:17Java EE authentication methods
- 35:08Demo: Cross-site request forgery
- 39:54Preventing CSRF with unique tokens
- 41:25Escaping dynamic content in JSP
- 44:04Conclusion and continuous learning
related talks
52mSecure Authentication and Session Management in Java EE
50mSecure Authentication and Session Management
42mSession Security in Web Applications
31mHow to Protect Yourself Against XSS Attacks in Java
54mWhat's New in Java EE Security: JSR-375 and Beyond
38mIdentity and Access Management in the 21st Century
42mWhat's New in Java EE 8: the Java EE Security API
56mHow to avoid vulnerabilities and adopt security best practices?
