Khanmarshai

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.

An authenticated SQL injection exists in the Syndromic Surveillance module. Users with Clinician-level privileges can read and modify arbitrary database contents by submitting crafted values to the `form icd codes[]` POST parameter at the 'syndromicsurveillance/index' endpoint. The issue allows the use of an unquoted numeric IN() clause and UNION DISTINCT SELECT statement with hex-encoded literals to abuse the MySQL `extractvalue()` function for error-based exfiltration of bcrypt password hashes. Additionally, stacked queries can be executed to reset passwords, leading to full administrative account takeover.

Stored cross-site scripting (XSS) exists in the Feature, Feature Link, Hero Image, and Image blocks. The issue occurs because the external link URL is insufficiently validated by the link filter and rendered without output escaping. A user with page-editing permissions can store a crafted external link value to inject arbitrary JavaScript. This script executes in the browser session of any user who views, previews, or edits the affected page, potentially leading to session hijacking and full administrative takeover.

An IP spoofing issue exists that allows unauthenticated remote attackers to bypass rate-limiting controls on self-hosted instances. By manipulating the `X-Forwarded-For` header through a misconfigured Nginx configuration, attackers can use the `$proxy add x forwarded for` directive to append arbitrary values to the header chain and present a fake IP address.

A low-privileged user with page creation permissions can perform stored Cross-Site Scripting (XSS) by injecting an `svg` element. This occurs because the XSS filter in the `detectXss()` function uses a regular expression for `on events` that fails to detect unquoted event handlers. The issue is located in the `system/src/Grav/Common/Security.php` file and affects the 'admin/pages/<page>' endpoint. This XSS can be escalated to exfiltrate sensitive system information from the '/admin/config/info' endpoint when visited by a Super Admin. An attacker can capture the `admin nonce`, which may be used to bypass CSRF protections and potentially lead to Remote Code Execution (RCE) and full server compromise.