T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:26- Finding
Excessive Filesystem and Command-Execution Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26-29
Vulnerability Type: Excessive tool permissions and violation of least privilege
Risk Level: Mediumyaml tools: - read - exec - writeTechnical Analysis
The skill requests unrestricted
read,write, andexeccapabilities even though its documented functionality consists primarily of music-platform recommendations, lyric templates, style matching, and music-theory guidance. No implementation in the audited package requires arbitrary filesystem access or general command execution.Granting these capabilities violates the principle of least privilege. If the hosting agent honors the declared tool list, instructions processed while this skill is active may access local files, alter data, or execute commands with the permissions of the agent process. The package contains no direct malicious command, but its unnecessarily broad authority increases the consequences of prompt injection, malicious future modifications, or unsafe user-supplied instructions.
Attack Path
- A host loads the skill and grants the tools declared in its metadata.
- The skill processes attacker-controlled or prompt-injected content during a music-related request.
- Malicious instructions direct the agent to invoke
read,write, orexec, despite those tools not being required for the legitimate task. - The agent reads accessible local information, changes files, or executes a command under the agent process's operating-system privileges.
- The resulting data exposure or system modification extends beyond the skill's stated music-guidance purpose.
This path depends on the host granting the declared tools and failing to independently constrain unsafe tool calls.
Impact Assessment
The potential scope is bounded by the permissions of the process running the agent. Possible impact includes:
- Reading local files accessible to the agent, ...[truncated 524 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
readandwrite, because the documented guidance and content-generation features do not require filesystem access. - Remove
execunless command execution is indispensable to a clearly defined feature. The optionalpingtroubleshooting advice does not justify unrestricted execution. - Prefer a tool-free Markdown skill for recommendations, lyric generation, prompt construction, and music-theory guidance.
- If external-service integration is later implemented, expose narrowly scoped platform APIs rather than a general shell.
- Where execution cannot be eliminated, enforce an explicit command allowlist, fixed arguments, timeouts, network restrictions, and sandboxing. Never concatenate untrusted input into commands.
- Require user confirmation before any filesystem or command-execution operation and restrict the agent to a dedicated workspace with minimal operating-system privileges.
- Add automated validation that rejects tool declarations not mapped to a documented and tested capability.
- Remove
