CyberRota Analysis
AI-GeneratedFlowise versions up to 3.1.4 are vulnerable to a server-side request forgery (SSRF) flaw that allows authenticated attackers to bypass the deny-list and issue arbitrary GET requests to sensitive cloud instance metadata services. This could lead to the exposure of instance identity data and role credentials on Oracle Cloud Infrastructure and Alibaba Cloud, potentially allowing unauthenticated access if public chatflows are involved. Organizations using Flowise in cloud environments should prioritize patching this vulnerability to mitigate the risk of credential exposure and unauthorized access.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts, where the DEFAULT_DENY_LIST omits the Oracle Cloud Infrastructure metadata endpoint 192.0.0.192 and the Alibaba Cloud metadata endpoint 100.100.100.200, allowing authenticated attackers to force the server to issue arbitrary GET requests to cloud instance metadata services. Attackers can send requests to the fetch-links API endpoint with a crafted URL parameter, bypassing deny-list validation including redirect-based bypasses, to reach instance metadata services and expose instance identity data and role credentials on Oracle Cloud Infrastructure or Alibaba Cloud deployments, with unauthenticated access possible when URL-fetching nodes exist in public chatflows.