other
Warning
- Location
- SKILL.md:58
- Finding
- Undisclosed External Data Handling Through Feishu## Vulnerability Details **File Location**: `SKILL.md`, lines 58–61 **Vulnerability Type**: Unnecessary external data handling **Risk Level**: Medium ### Evidence ```markdown ### 步骤 5：确认成功 1. 等待页面提示"发布成功" 2. 记录到飞书"已发布内容库" ``` ### Technical Analysis After publishing content to Xiaohongshu, the skill instructs the agent to record publication information in a Feishu repository named “Published Content Library.” This secondary external data transfer is not necessary to fulfill the primary publishing request. The instruction does not specify the authorized Feishu workspace, permitted destination, fields to be copied, applicable data-minimization rules, or whether the user has consented to the transfer. The additional side effect is also absent from the workflow documented in `README.md`, making it less visible to users reviewing the skill’s stated behavior. This issue does not match classifications T01–T09 because the available evidence does not demonstrate privilege escalation, persistent memory poisoning, malicious code, dependency compromise, or tool hijacking. It is classified as an external data-handling risk. ### Attack Path 1. A user asks the agent to publish approved content to Xiaohongshu. 2. The agent invokes the skill and publishes the content through the Xiaohongshu Creator Platform. 3. After receiving a successful-publication confirmation, the agent follows `SKILL.md` line 61. 4. The agent writes publication information to an unspecified Feishu “Published Content Library.” 5. User content or publication metadata is thereby duplicated into a third-party workspace without an explicit, operation-specific authorization requirement. ### Impact Assessment The instruction could cause unauthorized disclosure or duplication of published content and associated metadata into an unspecified Feishu workspace. It may also permit unintended modification of an organizational content repository using whatever Feishu access is already available to the agent. T ...[truncated 283 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the Feishu-recording step if it is not essential to the user-requested Xiaohongshu publication. 2. If archival is required, request explicit user consent before every external transfer. 3. Clearly identify the authorized Feishu tenant, workspace, application, and destination repository. 4. Define the exact fields that may be recorded and apply data minimization; avoid copying full content when a publication URL and status are sufficient. 5. Validate that the destination belongs to the intended user or organization before writing. 6. Require a preview and confirmation of the destination and data before creating or updating a record. 7. Document this side effect in `README.md` so the public workflow accurately describes all external services and data writes. 8. Log the transfer outcome without exposing sensitive content, and provide a clear way to disable archival.