Compliance Impact

The vulnerability allows unauthorized modification and reassignment of chatflows across workspaces, breaking tenant isolation in multi-tenant environments. This can lead to unauthorized access and modification of sensitive data, resulting in high confidentiality and integrity loss.

Such unauthorized access and data manipulation could potentially violate compliance requirements under standards like GDPR and HIPAA, which mandate strict controls on data access, integrity, and tenant isolation to protect personal and sensitive information.

Useful 0 Not Useful 0

Executive Summary

This vulnerability is a Mass Assignment issue in the chatflow update endpoint of FlowiseAI versions up to 3.1.1. It allows authenticated users to modify server-controlled properties of chatflows, such as deployment status, visibility, workspace assignment, and metadata, without proper validation or authorization.

Because the endpoint accepts client input without proper checks, an attacker can reassign chatflows to different workspaces, change their deployment state, or alter visibility settings. This breaks tenant isolation in multi-tenant environments and enables unauthorized cross-workspace resource reassignment and potential workflow takeover.

The issue was fixed in version 3.1.2.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized modification of chatflow objects, including changing their deployment status, visibility, and workspace assignment.

It breaks tenant isolation in multi-tenant environments, allowing attackers to reassign resources across workspaces and potentially take over workflows they should not have access to.

The impact includes high confidentiality and integrity loss, as sensitive data and workflow configurations can be manipulated by attackers with low privileges and no user interaction.

Useful 0 Not Useful 0

Detection Guidance

Detection of this vulnerability involves monitoring and analyzing requests to the chatflow update endpoint (PUT /api/v1/chatflows/{chatflowId}) for unauthorized modifications of server-controlled properties such as deployed, isPublic, workspaceId, createdDate, and updatedDate.

Specifically, look for authenticated user requests that attempt to change these sensitive attributes, which should normally be restricted.

Commands or tools to detect such activity could include using network traffic inspection tools like tcpdump or Wireshark to capture HTTP PUT requests to the chatflow update endpoint, combined with log analysis on the server side to identify unexpected changes in chatflow properties.

For example, using curl or similar tools to simulate or monitor requests might help in testing detection rules.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to upgrade Flowise to version 3.1.2 or later, where this mass assignment vulnerability has been patched.

Until the upgrade can be applied, restrict access to the chatflow update endpoint to trusted users only and monitor for suspicious activity involving modification of server-controlled properties.

Implement additional server-side validation and authorization checks to ensure that users cannot modify properties like deployed, isPublic, workspaceId, createdDate, and updatedDate.

Useful 0 Not Useful 0