Summary
Bludit contains a session fixation vulnerability where a user's session identifier can be set before authentication and remains unchanged after login.
An attacker who can cause a victim to use a chosen session ID may later hijack the victim's authenticated session once they log in.
Affected context
The vulnerability appears in Bludit's authentication and session management flow.
It is relevant in deployments where:
- Sessions are established or accepted before login
- The pre-authentication session ID is reused after the user successfully authenticates
- Users can be induced to visit crafted links or use attacker-controlled browsers or proxies
In such contexts, the same session token persists across the transition from anonymous to authenticated state.
Exploit preconditions
- Attack surface: Web application HTTP interface (typically via browser sessions and cookies)
- Required access: Ability to:
- Start a session with the application, and
- Get a victim to use the attacker-chosen session identifier (e.g., via crafted links, shared browsers, or controlled user agents)
- Trigger point: Victim logs in to their account while using the attacker-fixed session ID
- Why exploitation is possible: The application does not regenerate a fresh session identifier upon successful authentication, so the pre-auth session ID becomes the victim's authenticated session.
Why this happens
The underlying issue is improper session management at the time of authentication, mapped to CWE-384: Session Fixation.
Instead of invalidating the existing pre-authentication session and generating a new, unpredictable session identifier on successful login, the application continues to use the same session ID assigned before authentication.
This pattern allows an attacker who can influence or set the pre-login session token to later reuse that same token to access the authenticated session, effectively bypassing the need to know user credentials.
Potential impact
- Attacker may hijack a victim's authenticated session.
- Attacker can potentially access or modify the victim's account data.
- Actions may be performed on behalf of the victim, such as content creation, modification, or deletion.
- Attacker could chain this with other weaknesses (e.g., authorization flaws) to escalate impact across the application.
General mitigation guidance
Mitigation centers on robust session lifecycle management at authentication boundaries:
- Regenerate session identifiers on successful login and on privilege changes, invalidating old tokens.
- Avoid accepting externally supplied session identifiers where possible; let the server generate and manage them.
- Enforce short-lived session tokens with secure attributes (Secure, HttpOnly, SameSite) to reduce exposure.
- Design authentication workflows so that pre-authentication sessions carry minimal or no sensitive state and are treated as disposable.
- Ensure logout fully invalidates server-side session state rather than relying solely on client-side cookie removal.
How teams detect issues like this
Effective detection typically focuses on both design review and runtime behavior:
- Code review signals:
- Authentication workflows that do not explicitly regenerate session IDs on login.
- Direct reuse of session objects or identifiers across anonymous and authenticated states without reset.
- Static analysis patterns:
- Login handlers that set authentication flags or user identity on existing sessions without calling a session-regeneration API.
- Dynamic / behavioral testing:
- Capture a session ID before login, authenticate, and verify whether the session ID changes.
- Automated security tests or scanners configured to probe for session fixation.
- Policy enforcement:
- Security guidelines requiring session renewal on authentication and privilege changes, validated during security reviews and CI checks.

