Ido Shani

**Name of the Vulnerable Software and Affected Versions** Dify versions prior to 1.14.2 **Description** An authorization bypass allows authenticated editor users to set and enable trace configurations for any application, regardless of tenant ownership. This occurs due to missing tenant ownership checks in the trace configuration endpoints, enabling attackers to redirect all messages and responses from victim applications to LLM trace providers under their control. Dify Cloud facilitates this by allowing unauthenticated free self-registration for account creation. **Recommendations** Update to version 1.14.2 or later.

**Name of the Vulnerable Software and Affected Versions** Dify versions prior to 1.14.2 **Description** Insufficient URL path sanitization allows authenticated users to manipulate requests forwarded to the Plugin Daemon's internal REST API. By using unencoded dot sequences in task identifiers or manipulating the `filename` parameter in the plugin icon endpoint, attackers can perform path traversal to exit their authorized tenant path. This enables access to internal endpoints, such as debug interfaces, provided the attacker knows the victim tenant's UUID. In Dify Cloud environments, the risk is increased as free self-registration allows attackers to create accounts easily. **Recommendations** Update Dify to version 1.14.2 or later. As a temporary mitigation, restrict access to the `filename` parameter in the plugin icon endpoint to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Dify versions prior to 1.14.2 **Description** An authorization bypass exists in the file preview endpoint, allowing any authenticated user to read up to 3,000 characters of any uploaded document across all tenants and workspaces. This occurs because the system fails to verify ownership or workspace permissions when a file's UUID is provided. Attackers can exploit this by accessing the '/console/api/files/{file id}/preview' endpoint using an intercepted `file id`. Additionally, Dify Cloud permits unauthenticated free self-registration, which simplifies account creation for potential attackers. **Recommendations** Update to version 1.14.2 or later. As a temporary workaround, restrict access to the '/console/api/files/{file id}/preview' endpoint to minimize the risk of unauthorized document access.

**Name of the Vulnerable Software and Affected Versions** Dify versions prior to 1.14.0 **Description** An authorization bypass allows authenticated users to read the full contents of files uploaded by other users within the same tenant. This occurs due to insufficient permission verification in the 'chat-messages' endpoints, which fails to validate file ownership. By supplying an arbitrary file UUID in the `files` array of a 'chat-messages' request, attackers can bypass workspace separation and signed URL protections to retrieve sensitive file contents through workflow processing. **Recommendations** Update to version 1.14.0 or later.

**Name of the Vulnerable Software and Affected Versions** Chainlit versions prior to 2.9.4 **Description** Chainlit versions prior to 2.9.4 have an arbitrary file read issue in the /project/element update process. An authenticated client can manipulate a custom Element with a user-controlled path, leading the server to copy the specified file into the attacker’s session. The resulting element identifier (`chainlitKey`) can then be used to retrieve the file contents through the `/project/file/<chainlitKey>` API endpoint, potentially exposing any file accessible by the Chainlit service. This allows unauthorized disclosure of sensitive information like configuration files, databases, or source code. **Recommendations** Versions prior to 2.9.4 should be updated to version 2.9.4 or later.

**Name of the Vulnerable Software and Affected Versions** Chainlit versions prior to 2.9.4 **Description** Chainlit versions prior to 2.9.4 contain a server-side request forgery (SSRF) vulnerability in the `/project/element` update flow when configured with the SQLAlchemy data layer backend. An authenticated client can provide a user-controlled url value in an Element, which is fetched by the SQLAlchemy element creation logic using an outbound HTTP GET request. This allows an attacker to make arbitrary HTTP requests from the Chainlit server to internal network services or cloud metadata endpoints and store the retrieved responses via the configured storage provider. Server-Side Request Forgery (SSRF) occurs when a server fetches a remote resource without properly validating the user-supplied URL, potentially exposing internal services or sensitive data. On AWS clouds with older settings (IMDSv1), this could potentially lead to the theft of login credentials and full system takeover. **Recommendations** Versions prior to 2.9.4 should be updated to version 2.9.4 or later.