Information Disclosure in Flowise AI Chatbot Platform

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

Compliance Impact

This vulnerability allows an attacker with a valid API key for one workspace to retrieve full ChatFlow configurations, including sensitive data such as system prompts, node configurations, chatbotConfig, apiConfig, and credential IDs from other workspaces that have no API key assigned.

Such unauthorized disclosure of potentially sensitive configuration and credential information could lead to non-compliance with data protection standards and regulations like GDPR and HIPAA, which require strict controls over access to sensitive data and protection against unauthorized disclosure.

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

Detection Guidance

This vulnerability can be detected by testing the /api/v1/chatflows/apikey/:apikey endpoint on Flowise versions before 3.1.2. Specifically, you can make a request to this endpoint without including the keyonly query parameter and observe if chatflows from other workspaces without API keys are returned.

A possible command to test this could be using curl to query the endpoint with a valid API key but without the keyonly parameter, for example:

• curl -X GET "http://<flowise-server>/api/v1/chatflows/apikey/<valid_apikey>"

If the response includes chatflows from other workspaces that do not have an API key assigned, this indicates the vulnerability is present.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to upgrade Flowise to version 3.1.2 or later, where the vulnerability has been fixed by adding workspace scoping to the query.

Until the upgrade can be applied, restrict access to the /api/v1/chatflows/apikey/:apikey endpoint to trusted users only, and avoid sharing API keys across workspaces.

Additionally, monitor API usage for unusual access patterns that might indicate exploitation attempts.

Useful 0 Not Useful 0