T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:35- Finding
Excessive Tool Permissions for an Art-Guidance Skill
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:35-38
Vulnerability Type: Excessive tool permissions and violation of least privilege
Risk Level: Mediumyaml tools: - read - exec - writeTechnical Analysis
The skill declares
read,write, andexeccapabilities despite its stated purpose being to provide art-creation guidance, technique development, and appreciation advice. General command execution and unrestricted filesystem modification are not demonstrably required for that purpose.The document does not define a command allowlist, filesystem path restrictions, user-confirmation requirements, permitted external endpoints, or restrictions on the data that may be processed. Although the document recommends sandboxing and allowlisted commands elsewhere, those recommendations are descriptive and are not represented by enforceable controls in the project.
The audited project contains only
SKILL.md; no executable implementation was present. Consequently, no active malicious payload or demonstrated command-injection implementation was found. The risk arises when an Agent platform grants the declared capabilities and interprets the skill's broad processing instructions as authorization to use them.Attack Path
- A user installs or loads the skill into an Agent platform.
- The platform grants the skill its declared
read,write, andexectools. - The skill processes user-controlled art content or file-related input.
- Without enforceable path, command, or confirmation restrictions, manipulated input may induce the Agent to read unrelated files, modify accessible files, or execute commands outside the legitimate art-guidance task.
- Any resulting access is limited by the operating-system privileges, sandbox controls, and credentials of the hosting Agent process.
Impact Assessment
If the declared tools are granted without external sandbox enforcement, the skill ...[truncated 591 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
execbecause command execution is not necessary for conversational art guidance. - Remove
writeunless a documented feature specifically requires creating user-requested output files. - Retain
readonly when analysis of a user-selected artwork or document is required. - Restrict file access to paths explicitly selected by the user and deny traversal outside the designated workspace.
- If writing is retained, require explicit confirmation for each destination and prevent overwriting existing files by default.
- If command execution is indispensable, use an enforceable command-and-argument allowlist, prohibit shell interpretation, reject user-controlled command fragments, run commands in an isolated sandbox, and apply operating-system resource limits.
- Require per-operation user approval for sensitive tool calls and display the exact path or command before execution.
- Restrict network access to explicitly documented HTTPS endpoints and prevent transmission of local files, environment variables, API keys, or other secrets.
- Update the capability declaration and documentation so that every requested permission maps to a concrete, narrowly scoped feature.
- Remove
