An unauthenticated attacker using a raw WebSocket client can ignore the redirect frame and continue to send event-dispatching frames. Since the handle_event logic in these versions assumes the mount-time authentication checks are sufficient, it fails to re-verify the session status, allowing for the execution of sensitive event handlers. This bypass is critical for applications that rely solely on mount-level decorators and do not perform independent authorization checks inside individual event handler methods.

Attack Chain

1. Attacker initiates an unauthenticated WebSocket connection to a LiveView endpoint protected by login_required.
2. Server's LiveViewConsumer performs the mount check and triggers a redirect response (navigate frame) due to missing authentication.
3. Attacker's custom WebSocket client parses the redirect frame but intentionally refuses to close the connection or navigate away.
4. Server keeps the underlying WebSocket connection open and fails to clear self.view_instance from memory.
5. Attacker sends a malformed {"type":"event", ...} frame targeting an @event_handler on the gated view.
6. The LiveViewConsumer processes the event frame, bypassing any further security checks, and invokes the target method.
7. The application logic executes the sensitive handler with an unauthenticated session, resulting in unauthorized data access or state mutation.

Impact

Successful exploitation allows unauthenticated users to invoke sensitive server-side functions within gated views. Impact ranges from unauthorized information disclosure to data manipulation depending on the functionality of the exposed event handlers. Exploitation requires knowledge of specific view paths and event handler names. All djust applications using gated LiveViews on versions prior to 1.0.4 are affected.

Recommendation

• Update to djust version 1.0.4 or later immediately to apply the patch provided in commit 1ae8aa9.
• For legacy deployments where patching is not immediately possible, implement explicit authentication and authorization checks at the top of every @event_handler within gated views.
• Enable the defense-in-depth configuration LIVEVIEW_CONFIG['reauth_on_event'] = True to mandate session re-verification for all event handlers in gated views.
• Audit application code for LiveView event handlers that perform mutations without secondary validation against the current session user.