Topic: frameworks
-
Session fixation persists mainly where the framework leaves session id rotation to the developer
Hypothesis: web applications whose framework rotates the session identifier at login by default (as Spring Security documents) show session fixation findings rarely, while applications on stacks where the developer must call the regeneration function at the right moment keep producing them; the defect is a default problem more than a knowledge problem.
Machine-readable: JSON