T09 · Insecure Skill Coding Practices
- Location
references/templates.md:43- Finding
Unredacted Persistence of Authorization-Bearing API Responses
- Content
View full analysis
` ## Evidence Checklist - Save request payloads and API responses under `output/aliyun-vod-manage/`. - Keep a mapping of input file names to returned media IDs. ``` The affected instruction is: ```markdown - Save request payloads and API responses under `output/aliyun-vod-manage/`. ``` ### Technical Analysis The evidence policy instructs the agent to persist complete request payloads and API responses without requiring secret-field redaction, restrictive file permissions, encryption, or retention limits. This workflow explicitly includes authorization-producing operations such as `CreateUploadVideo` and `GetVideoPlayAuth` in `references/templates.md:5-25`. Responses from these operations may contain temporary upload credentials, upload authorization data, playback authorization material, or signed resource information. Persisting complete responses can therefore place reusable authorization data in plaintext under the output directory. The risk is not caused by the metadata-download script, which only retrieves public OpenAPI metadata and does not access credentials. It arises when the broader Skill workflow applies the evidence instruction to authenticated VOD operations. ### Attack Path 1. A user invokes the Skill for an operation such as `CreateUploadVideo` or `GetVideoPlayAuth`. 2. Alibaba Cloud returns temporary upload or playback authorization material. 3. Following the evidence checklist, the agent saves the complete API response under `output/aliyun-vod-manage/`. 4. The generated file inherits default filesystem permissions and remains available without a defined deletion period. 5. Another local user, a ...[truncated 953 chars]- Remediation
View remediation
