Summary
BigBlueButton versions before 3.0.23 exposed an internal controller action that allowed a requester who knew an active participant's identifier to reuse that participant's meeting session. This could let the requester impersonate the participant within the same virtual classroom.
Affected context
The issue occurs in BigBlueButton deployments that expose the handleJoinExistingUser controller action through the web API. The action was routable even though it was intended to function as an internal helper, and an active participant identifier could be supplied to join an existing session. Exploitability depends on the endpoint being reachable and a valid participant identifier being obtainable.
Exploit preconditions
- Attack surface: The BigBlueButton web application API endpoint associated
with handleJoinExistingUser.
- Required access: Network access to the affected BigBlueButton service and
knowledge or discovery of an existing active participant identifier.
- Trigger point: A request that invokes the exposed controller action with
an existingUserID for an active meeting participant.
- Why exploitation is possible: The application does not adequately
authenticate or authorize the request before reusing the participant's
existing session.
Why this happens
The underlying flaw is an authorization boundary failure in which an internal session-reuse operation was exposed as a routable controller action. The application treated possession of an existing participant identifier as sufficient to access that participant's session, rather than verifying that the requester was authorized to act as that participant. This behavior maps to CWE-287, Improper Authentication.
Potential impact
- An attacker may impersonate an active meeting participant.
- An attacker could access or interact with meeting resources available to that participant.
- An attacker may send messages, participate in activities, or alter the participant's presence.
- Meeting confidentiality, integrity, and trust could be affected.
General mitigation guidance
Mitigation generally focuses on keeping internal helpers private and ensuring every session-reuse operation performs explicit authentication and authorization. Secure-by-default designs should use narrowly scoped, short-lived, audience-bound join tokens instead of reusable participant identifiers. Input trust should be reduced by treating identifiers as untrusted references, validating their context, and requiring proof of ownership or an authorized meeting role. Session operations should run with least privilege, and sensitive actions should be protected by consistent access-control policy enforcement.
How teams detect issues like this
Detection can include static analysis and code review rules that flag controller methods exposing internal helpers, session adoption based only on user-supplied identifiers, and missing authentication or authorization checks on join-related routes. Reviewers can examine whether identifiers are guessable, reusable, or accepted without meeting and user-context validation. Runtime monitoring and policy enforcement can look for unusual calls to existing-session endpoints, repeated identifier probing, and session joins that do not follow the expected authenticated flow. Automated security review tools may help identify these patterns.

