T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:27- Finding
Unnecessary Command-Execution Permission for a Documentation-Only Skill
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27–30
Supporting Locations:SKILL.md, line 329 documents a Markdown-only purpose; line 372 recommends administrator execution when troubleshooting permission errors.
Vulnerability Type: Excessive tool permissions and potential privilege escalation
Risk Level: MediumVulnerable Code Snippet
yaml tools: - read - exec - writeTechnical Analysis
The skill requests the
exectool even though its documented function is limited to generating and reviewing Markdown API documentation. This activity ordinarily requires only constrained access to read source material and write user-approved documentation files.Granting command-execution capability violates least-privilege principles and expands the security boundary from document manipulation to arbitrary local process execution. The risk is compounded by the troubleshooting guidance at line 372, which recommends running with administrator privileges when read or write permissions are insufficient. The skill does mention command allowlisting at line 183, but no enforceable allowlist or command restrictions are defined.
There is no evidence that the skill currently contains or retrieves a malicious command. The vulnerability is therefore an excessive-capability condition: malicious, compromised, or attacker-controlled input could potentially influence an agent that has loaded the skill into invoking commands beyond the skill's legitimate purpose.
Attack Path
- A user loads the skill, granting its declared
read,write, andexeccapabilities. - The agent processes attacker-controlled or otherwise untrusted API descriptions, documentation content, file names, or troubleshooting instructions.
- Crafted input attempts to persuade the agent to invoke the unnecessary
execcapability. - If a permission error occurs, the documented troubleshooting advice may encourage the user to restart or run the environment with ...[truncated 1015 chars]
- A user loads the skill, granting its declared
- Remediation
View remediation
Remediation Suggestions
- Remove
execfrom the skill manifest because no documented workflow requires shell-command execution:
yaml tools: - read - write- Restrict
readandwriteaccess to explicit user-approved project and documentation paths. - Replace the administrator-execution recommendation with least-privilege troubleshooting, such as verifying ownership, selecting a writable output directory, or granting only the minimum file permission required.
- If command execution becomes necessary in a future version, define a narrow and enforceable command allowlist rather than relying on advisory text.
- Require explicit user confirmation before every command invocation and display the exact command, arguments, working directory, and intended effect.
- Prevent untrusted input from being interpolated into shell commands. Use structured process APIs with fixed executable paths and separately supplied arguments.
- Run the skill in a sandbox without elevated privileges and deny access to unrelated files, credentials, and network resources.
- Add automated manifest validation that rejects permissions not justified by a documented workflow.
- Remove
