FlowiseAI CSVAgent RCE Vulnerability Analysis and PoC

Summary of FlowiseAI/Flowise Remote Code Execution Vulnerability Vulnerability Overview A Remote Code Execution (RCE) vulnerability exists in the component of FlowiseAI. An attacker can inject base64-encoded Python code into Flowise's Python source string by crafting a malicious data URI, thereby executing arbitrary code on the server. Affected Versions Affected Versions: FlowiseAI and Flowise-components versions . Fixed Version: . Mitigation Upgrade to FlowiseAI and Flowise-components version . POC Code 1. 2. 3. Verification Steps 1. 2. 3. UI: create admin + dummy OpenAI credential (any string for the API key — never validated, the exploit fires before the LLM is invoked) 4. Plant the attached in the chatflows DB (UI import or POST ) 5. Open the chatflow — click chat — send any message 6. Chat panel shows 7. is now present, 40 bytes, content , owner:uid matches the Flowise process uid 4. Verification Results End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack verified: End-to-end attack verified on a cloned repository (commit ), which is based on the PoC. End-to-end attack

Goal Reached Thanks to every supporter — we hit 100%!

FlowiseAI CSVAgent RCE Vulnerability Analysis and PoC

More from this source