Threat Intelligence Database

Coze Studio versions up to 0.5.1 contain an insecure direct object reference vulnerability that allows authenticated users to bypass authorization controls. By supplying foreign workflowIDs paired with their own spaceID, attackers can access, modify, run, or delete workflows belonging to other tenants. This affects multiple API routes including save, update_meta, batch_delete, canvas, test_run, and nodeDebug.

Coze Studio versions before 0.5.0 have an insecure default configuration that allows any registered user to execute arbitrary commands by running workflow code nodes in an unsandboxed Python 3 subprocess. Attackers can bypass the regex import filter using __import__('subprocess') to execute commands, potentially stealing environment variables, model API keys, and accessing backend services such as 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.

A vulnerability was detected in ByteDance coze-studio up to 0.5.1. Affected by this vulnerability is the function ExecuteSQL of the file backend/domain/memory/database/service/database_impl.go of the component databaseTool. Performing a manipulation results in sql injection. The attack can be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.