Coze Studio vulnerabilities

Coze Studio through 0.5.1 fails to restrict the server URL supplied when registering plugin tools, allowing authenticated users to make the backend fetch internal services. Attackers can construct plugin requests to access cloud metadata endpoints and internal services reachable only from the backend network, reading responses containing sensitive information.

Coze Studio through 0.5.1 fails to validate that table names in workflow SQL customization nodes belong to the caller's workspace. Authenticated attackers can enumerate predictable table identifiers and execute SQL statements against other workspaces' memory databases to read, insert, or delete data.

coze-studio up to 0.2.4 uses a hard-coded cryptographic key in backend/domain/plugin/encrypt/aes.go (AuthSecretKey/StateSecretKey/OAuthTokenSecretKey). The attack can be remote but is considered difficult and highly complex. The vendor recommended deploying a patch and plans user-defined key management via configuration.