جزئیات آسیب‌پذیری

Dify before 1.15.0 contains a server-side request forgery vulnerability that allows any authenticated console user to bypass SSRF protections and issue arbitrary HTTP requests to internal services and cloud metadata endpoints due to the Squid proxy configuration only defining source ACLs without destination deny rules and the make_request() helper performing no independent destination IP validation. Attackers can use endpoints such as GET /console/api/remote-files/<url>, POST /console/api/remote-files/upload, the HTTP Request workflow node, website crawl, or document import from URL to reach internal components like the sandbox, internal APIs, and PostgreSQL, and on AWS deployments read IAM credentials from the instance metadata service, with the HTTP Request node further enabling POST, PUT, and DELETE writes to internal services relying on network isolation for authorization.

• https://github.com/langgenius/dify/releases/tag/1.15.0 release-notes
• https://github.com/langgenius/dify/pull/36332 issue-trackingpatch
• https://github.com/langgenius/dify/commit/7bfcf9185c75bb18f0b44335080524e659f087d9 patch
• https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints third-party-advisory