Mitigation Strategies

To mitigate this vulnerability in Flowise versions prior to 2.1.4, you should disable the overrideConfig feature by default.

Implement an explicit allow-list of permitted variables to restrict configuration injection.

Remove the use of the vm2 sandbox and replace it with a more secure alternative such as the isolated-vm package.

Useful 0 Not Useful 0

Executive Summary

The vulnerability in Flowise before version 2.1.4 involves the overrideConfig feature, which allows configuration injection into the Chainflow during execution. This feature is enabled by default and lacks an allow-list of permitted variables. Because Flowise relies on the vm2 sandbox for security, which can be bypassed, an attacker can exploit this to perform remote code execution, escape the sandbox, cause denial of service by crashing the server, perform server-side request forgery, inject prompts, and exfiltrate server variables and data.

This vulnerability affects both the frontend web integration and the backend Prediction API. Although the issues are self-targeted and do not persist to other users, they pose significant risks to the server and business.

Useful 0 Not Useful 0

Impact Analysis

Exploitation of this vulnerability can lead to several severe impacts including remote code execution on the server, allowing attackers to run arbitrary code.

• Sandbox escape, bypassing security restrictions intended to isolate code execution.
• Denial of service by crashing the server, potentially making the service unavailable.
• Server-side request forgery (SSRF), enabling attackers to make unauthorized requests from the server.
• Prompt injection and full control over large language model (LLM) prompts.
• Exfiltration of server variables and data, risking sensitive information leakage.

While these impacts are self-targeted and do not affect other users directly, they expose the server and business to significant security risks.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability in Flowise before version 2.1.4 allows attackers to perform remote code execution, sandbox escape, denial of service, server-side request forgery, prompt injection, and data exfiltration. These security risks expose the server and business to potential unauthorized access and data breaches.

Although the issues are self-targeted and do not persist to other users, the ability to exfiltrate server variables and data could lead to violations of data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches.

Therefore, organizations using affected versions of Flowise may face compliance challenges if this vulnerability is exploited, as it undermines the confidentiality, integrity, and availability of data required by these standards.

Useful 0 Not Useful 0