T09 · Insecure Skill Coding Practices
- Location
SKILL.md:31- Finding
Shell Command Injection Through Untrusted Meeting Content in Feishu Sync Workflow
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is for meeting minutes, but its Feishu sync command is unsafe and it can share or store meeting content without clear consent.
Install only if you are comfortable reviewing each Feishu sync and local action-item save before it happens. Do not run the documented Feishu shell command with untrusted meeting text; use a safer argument-array or file-based workflow instead.
SKILL.md:31Shell Command Injection Through Untrusted Meeting Content in Feishu Sync Workflow
The code partially aligns with the 'create meeting minutes templates/customize meeting formats' portion of the description because it renders a meeting-minutes template with provided values. However, it does not implement several prominent declared capabilities: it does not parse discussion notes, does not generate structured minutes from raw notes, does not sync anything to Feishu, and does not manage or track action items. Its actual purpose is much narrower: template rendering for meeting minutes. Therefore the description materially overstates the implemented behavior.
The skill instructs the agent to read a template file and write action-item data to local memory, but it declares no explicit tool scope or permissions. This creates an authorization gap where file access may occur without clear user or platform constraints, increasing the chance of unintended file reads/writes or future expansion of the skill beyond its stated boundaries.
The invocation criteria are broad enough to trigger on generic meeting-related context, which can cause the agent to activate this skill when the user did not explicitly request note generation, syncing, or tracking. In this skill's context, over-triggering is more dangerous because it can lead to unintended processing of sensitive meeting content and downstream storage or external sharing.
The Feishu sync section encourages creating a document and sharing it with attendees, but it does not require a user-facing consent step or warn that potentially sensitive meeting content will be sent to an external service and possibly shared. In the context of meeting minutes, this is especially risky because notes often contain confidential business discussions, personnel matters, or strategic decisions.
The skill saves extracted action items to a local memory file without warning the user that meeting-derived data will be persisted. Because action items may include names, deadlines, internal projects, or sensitive follow-up tasks, silent local retention creates privacy and data-governance risks.
No suspicious patterns detected.