Vulnerability · Published Aug 29, 2025 · Assigned by VulDB
CVE-2025-9604coze-studio aes.go hard-coded key
Low 3.7
In plain English
A low-severity security flaw in coze-studio. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities).
Official description
A vulnerability was identified in coze-studio up to 0.2.4. The impacted element is an unknown function of the file backend/domain/plugin/encrypt/aes.go. The manipulation of the argument AuthSecretKey/StateSecretKey/OAuthTokenSecretKey leads to use of hard-coded cryptographic key . It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is regarded as difficult. To fix this issue, it is recommended to deploy a patch. The vendor replied to the GitHub issue (translated from simplified Chinese): "For scenarios requiring encryption, we will implement user-defined key management through configuration and optimize the use of encryption tools, such as random salt."
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| n/a | coze-studio | 0.2.00.2.10.2.20.2.30.2.4 |
Weakness: CWE-321, CWE-320 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C
References
- VDB-321780 | coze-studio aes.go hard-coded key vdb-entry, technical-description
- VDB-321780 | CTI Indicators (IOB, IOC, TTP, IOA) signature, permissions-required
- Submit #636417 | coze-dev coze-studio <0.2.4 Cryptographic Issues third-party-advisory
- https://github.com/coze-dev/coze-studio/issues/505 issue-tracking
- https://github.com/coze-dev/coze-studio/issues/505#issuecomment-3148568862 issue-tracking
- https://github.com/coze-dev/coze-studio/pull/533 issue-tracking, patch