Summary
Opencast's default security configuration accepts a client-selected session identifier from a URL path parameter and may retain it after login. An unauthenticated attacker can send a crafted link to a victim, reuse the known identifier after authentication, and access the victim's session, potentially including administrative capabilities.
Affected context
The issue occurs in Opencast deployments using the affected default security configuration when session identifiers supplied through URL path parameters are accepted and are not replaced during authentication. Exploitation is most relevant when a victim follows an attacker-controlled link before establishing an active Opencast session and subsequently logs in through that session.
Exploit preconditions
- Attack surface: Opencast web authentication and session handling
- Required access: No prior Opencast account or authenticated access is required for the attacker; the attacker must be able to deliver a crafted link to a victim
- Victim condition: The victim's browser must not already have an active Opencast session cookie
- Trigger point: The victim authenticates after visiting a URL containing an attacker-selected session identifier
- Why exploitation is possible: The server may associate the selected identifier with the authenticated session instead of regenerating it at login
Why this happens
The vulnerability is caused by failing to invalidate or rotate a session identifier when authentication status changes. Accepting a client-controlled identifier through a URL path parameter and preserving it after login allows an attacker to know the identifier associated with the victim's authenticated session. This behavior maps to CWE-384: Session Fixation, where an attacker can establish or predict a session identifier before authentication and reuse it afterward.
Potential impact
- An attacker may access the victim's authenticated session
- Victim data and account actions could be exposed or misused
- Unauthorized changes could be performed under the victim's identity
- An administrator's account could be fully taken over
- The Opencast installation could be affected through compromised administrative privileges
General mitigation guidance
Mitigation generally focuses on enforcing secure session lifecycle behavior and reducing trust in client-provided identifiers.
Common defensive patterns include:
- Regenerating and replacing session identifiers whenever authentication state changes
- Rejecting or disabling URL-based session identifiers where they are not required
- Restricting accepted session identifiers to server-issued, securely scoped cookies
- Applying secure, HttpOnly, and SameSite cookie attributes appropriate to the deployment
- Invalidating pre-authentication sessions after successful login
- Limiting administrative privileges and requiring additional protections for sensitive actions
- Enforcing security-focused configuration defaults across all deployment environments
These controls reduce the likelihood that a known pre-authentication identifier can become an authenticated session.
How teams detect issues like this
Organizations can identify session fixation risks through:
- Static and configuration analysis for URL-based session tracking and client-selected session identifiers
- Code review checks confirming session identifiers are rotated after login, privilege changes, and reauthentication
- Integration tests that verify pre-authentication identifiers cannot be reused after authentication
- Web application monitoring for authenticated requests using identifiers first observed before login
- Policy enforcement requiring cookie-based session management and secure session attributes
- Automated security testing or code review tools that flag missing session regeneration and insecure session configuration

