Flowise Sensitive Data Exposure Vulnerability in public-chatbotConfig Endpoint

A vulnerability in Flowise prior to version 3.1.0 allows for the unauthorized exposure of sensitive data through the public-chatbotConfig API endpoint. This endpoint reveals API keys, HTTP authorization headers, and internal configuration details without requiring authentication. An attacker who knows a chatflow UUID can access credentials stored in password fields and HTTP headers, leading to credential theft. The issue affects all Flowise Cloud users with chatflows containing password-type fields or HTTP headers, as well as self-hosted Flowise instances exposed to the internet.

Impact

The vulnerability allows for unauthorized access to sensitive data, including API keys and HTTP authorization headers, which can be exploited for credential theft and potentially more severe consequences.

Reproduction

To reproduce this vulnerability, create a chatflow in Flowise and include a node that stores an API key in a password-type field, such as the 'Unstructured API Key' field in an S3 File node. Alternatively, add a 'Requests Post' node with an Authorization header. Once the chatflow is saved, the UUID can be used to access the public-chatbotConfig API endpoint, which will return the flowData object containing the exposed API key and Authorization token.

Remediation

Users can update to Flowise version 3.1.0 or later, where this vulnerability has been fixed.