Skip to content
soovwv/cve·Indexed by this site · Originally publishedDate not given· Event →· Its place in the scan record →

Researchers say authenticated users of Flowise 3.1.4 can bypass SSRF protection via subpath imports

Flowise SSRF Protection Bypass via Subpath Imports

AI summary

Researchers disclosed an SSRF protection bypass in Flowise: switching Custom Function to a subpath import of the same package bypasses the sandbox's SSRF protection with no configuration required. The cause is that the vm2 sandbox installs security wrappers under the exact module names axios and node-fetch, and a subpath resolves to the real, unwrapped HTTP client, so the denylist, DNS rebinding protection and per-hop redirect re-validation all fail to take effect. The vulnerability was confirmed at runtime in 3.1.4 (the final version), and the vulnerable code pattern dates back to 3.0.13; the repository has been archived and there is no vendor patch. An authenticated user with permission to edit flows can use this to enumerate internal networks, read services bound only to loopback and write to internal networks, and the block on the cloud metadata address 169.254.169.254 is likewise bypassed (verified in a self-hosted environment; no real credentials were obtained).

Read originalgithub.com