Executive Summary

This vulnerability exists in Flowise versions before 3.1.2 and involves an information disclosure issue in the /api/v1/chatflows/apikey/:apikey endpoint. When the keyonly query parameter is not provided (which is the default behavior), the endpoint returns not only the chatflows associated with the supplied API key but also all chatflows across every workspace that do not have an API key assigned. This happens because the underlying query does not filter by workspace.

As a result, an attacker who has a valid API key for one workspace can retrieve the full ChatFlow configuration of unprotected chatflows belonging to other workspaces. This configuration includes sensitive details such as flowData with system prompts and node configurations, chatbotConfig, apiConfig, and credential IDs.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive configuration data from other workspaces that are not protected by an API key. An attacker with access to one workspace's API key can access detailed ChatFlow configurations of other workspaces, potentially exposing system prompts, node configurations, chatbot settings, API configurations, and credential identifiers.

Such exposure could allow attackers to understand or manipulate chatbot behavior, gain insights into system operations, or use credential IDs for further attacks, thereby compromising confidentiality and potentially leading to further security breaches.

Useful 0 Not Useful 0