coze-dev vulnerabilities and threats

Coze Studio through 0.5.1 contains an insecure direct object reference vulnerability in workflow.go that allows authenticated users to access other spaces' workflows by supplying foreign workflowIDs. Attackers can pair their own spaceID with another tenant's workflowID in save, update_meta, batch_delete, canvas, test_run and nodeDebug routes to read, run, overwrite or delete workflows.

Coze Studio before 0.5.0 contains an insecure default configuration that allows any registered user to execute commands by running workflow code nodes in an unsandboxed python3 subprocess. Attackers can bypass the regex import filter with __import__('subprocess') to run commands, stealing environment variables, model API keys, and accessing MySQL, MinIO, Redis and etcd.

Coze Studio versions up to 0.5.1 contain a Server-Side Request Forgery (SSRF) vulnerability that allows authenticated users to make the backend server fetch internal services by supplying arbitrary server URLs when registering plugin tools. This can lead to unauthorized access to cloud metadata endpoints and internal services accessible only from the backend network, potentially exposing sensitive information.

Coze Studio versions up to 0.5.1 contain an authorization flaw where SQL customization nodes do not verify that table names belong to the caller's workspace. This allows authenticated attackers to enumerate table identifiers and perform unauthorized SQL operations on other workspaces' memory databases, including reading, inserting, or deleting data. The vulnerability has a high severity with a CVSS score of 8.7.