Executive Summary

This vulnerability is a mass assignment flaw in the tool update endpoint of FlowiseAI versions prior to 3.1.2. Authenticated users can modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating a tool resource. Because the server lacks proper validation and authorization checks, an attacker can manipulate the workspaceId field to reassign tools to arbitrary workspaces.

This means the attacker can break tenant isolation in environments where multiple workspaces exist by moving tools between workspaces without permission. The root cause is that the server merges user-supplied JSON data directly into the database entity without restricting which fields can be modified.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability allows an attacker with low privileges to reassign tools to different workspaces, breaking tenant isolation in multi-workspace environments. This can lead to unauthorized access and modification of tools and their metadata across workspaces.

The impacts include high confidentiality and integrity risks because attackers can manipulate data they should not have access to. However, availability is not affected by this vulnerability.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by monitoring and inspecting requests to the tool update endpoint of FlowiseAI, specifically the PUT /api/v1/tools/{toolId} API call.

Look for authenticated requests that include unexpected or unauthorized modifications to server-controlled properties such as workspaceId, createdDate, or updatedDate in the JSON request body.

Commands or methods to detect this may include:

• Using network traffic capture tools (e.g., tcpdump, Wireshark) to capture HTTP PUT requests to /api/v1/tools/* and analyze the JSON payload for unauthorized fields.
• Using API gateway or web application firewall (WAF) logs to identify requests modifying workspaceId or other server-controlled fields.
• If you have access to the server logs, search for update requests where workspaceId or createdDate/updatedDate fields are changed by users who should not have such permissions.
• Example command to capture relevant HTTP requests with tcpdump (replace <interface> with your network interface): tcpdump -i <interface> -A -s 0 'tcp port 80 or tcp port 443' | grep -i 'PUT /api/v1/tools/'

Useful 0 Not Useful 0

Mitigation Strategies

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

Until the upgrade can be performed, restrict access to the tool update endpoint to only trusted and authorized users to reduce the risk of exploitation.

Implement additional server-side validation and authorization checks to ensure that users cannot modify server-controlled properties such as workspaceId, createdDate, and updatedDate.

Monitor logs and network traffic for suspicious activity involving modification of these fields.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability allows authenticated users to manipulate workspace assignments and metadata without proper authorization, breaking tenant isolation in multi-workspace environments.

This unauthorized access and modification can lead to confidentiality and integrity breaches of data across different tenants or workspaces.

Such breaches may impact compliance with standards and regulations like GDPR and HIPAA, which require strict access controls and data segregation to protect personal and sensitive information.

Useful 0 Not Useful 0