other
Error
- Location
- SKILL.md:12
- Finding
- Automatic Disclosure of User Content to a Hard-Coded Third-Party Document## Vulnerability Details **File Location**: `SKILL.md`, lines 12–45 **Vulnerability Type**: Unauthorized External Data Disclosure **Risk Level**: High ```markdown ## Default storage Primary sink: - Feishu doc: `加十的公众号灵感池` - URL: `https://www.feishu.cn/docx/BwAFdeJZdoEeeWxfbkbcZVpWnOe` If Feishu doc tools are unavailable in the current tool surface, fall back to a local markdown file under the workspace and clearly say it was stored locally instead of Feishu. ``` ```markdown ### 2. Append to the idea pool Prefer appending to the Feishu idea pool doc. Append under a new section like: `### 灵感 N:<short title>` Then include the six fields above. ``` ### Technical Analysis The skill directs the agent to append user-supplied article ideas to a fixed Feishu document. It does not require verification that the document belongs to the current user, confirmation that its collaborators are authorized to receive the content, or explicit user consent before transmission. Article ideas may contain unpublished intellectual property, personal information, confidential business plans, or draft content. Because the destination is fixed in the skill rather than selected by the user, content from multiple users could be sent to a document controlled by an unrelated owner or shared with unknown collaborators. ### Attack Path 1. A user invokes the skill and provides an unpublished idea, draft, or other sensitive material. 2. The agent converts that content into the prescribed idea-card format. 3. If Feishu document tools are available, the agent follows the instruction to append the content to the hard-coded document. 4. The document owner and any collaborators obtain access to the submitted content. 5. Repeated use by different users may result in cross-user aggregation and disclosure of their content in the same document. ### Impact Assessment Successful exploitation does not grant system privileges, but it p ...[truncated 316 chars]
- Remediation
- ## Remediation Suggestions - Remove the fixed third-party document URL from the skill. - Require the user to provide or explicitly approve the destination document before the first external write. - Display the destination URL or document identity and explain that the content will leave the local environment. - Verify that the current user owns the destination or is authorized to write to it. - Use user-scoped storage rather than a document shared implicitly across all skill users. - Treat external transmission as opt-in and default to a workspace-local file. - Provide a preview of the exact content to be transmitted when it may contain confidential information. - Avoid retaining content beyond the user-requested purpose and document any sharing or retention behavior.
