flowise
Affected
- introduced
0, fixed2.1.4(semver)
Fixed versions
2.1.4
Fix
- Fixed version
2.1.4npm install [email protected]
Advisory
Also known as: CVE-2024-58351
Flowise OverrideConfig security vulnerability
Impact
Flowise allows developers to inject configuration into the Chainflow during execution through the overrideConfig option. This is supported in both the frontend web integration and the backend Prediction API.
This has a range of fundamental issues that are a major security vulnerability.
While this feature is intentional, it should have strong protections added and be disabled by default.
These issues include:
And many many more such as altering the flow of a conversation, prompt exfiltration via LLM proxying etc.
These issues are self-targeted and do not persist to other users but do leave the server and business exposed.
All issues are shown with the API but also work with the web embed.
Workarounds
overrideConfig should be disabled by defaultoverrideConfig should have an explicit allow list of variables that are allowed to be modified. This way the user opts-in to where modifications can be made. vm2 and any forks of it should be removed as in the authors own words, "fixing the vulnerability seems impossible". The recommended replacement is https://www.npmjs.com/package/isolated-vmHigh Basis: The source's own band: HIGH
0, fixed 2.1.4 (semver)2.1.4
2.1.4npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0