T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:5- Finding
Excessive and Inconsistent Tool Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:5andSKILL.md:17-20
Vulnerability Type: Excessive tool privileges and inconsistent access-control declarations
Risk Level: MediumVulnerable Configuration
yaml allowed-tools: read execyaml tools: - exec - read - writeTechnical Analysis
The Skill is described as a text-based assistant for producing creative strategies, visual-style guidance, and marketing concepts. These ordinary functions do not require arbitrary command execution or unrestricted filesystem access.
Nevertheless, the configuration declares
exec,read, andwritecapabilities. The permission declarations are also inconsistent:writeappears in thetoolslist but is absent fromallowed-tools. Depending on how the hosting Agent resolves this discrepancy, it may grant the broader permission set or behave unpredictably.The document also claims command execution, API integration, and general file-processing capabilities near
SKILL.md:207-210, but it does not define enforceable command allowlists, permitted filesystem paths, destination allowlists, write confirmation requirements, or sandbox boundaries. Merely advising that only allowlisted commands should be used does not implement such a control.No instruction in the reviewed file directly attempts to abuse these privileges. The issue is a violation of least privilege that unnecessarily expands the consequences of prompt manipulation or unsafe host behavior.
Attack Path
- A hosting Agent loads the Skill and interprets one or both tool declarations.
- The platform grants filesystem or command-execution capabilities to the Skill.
- Untrusted task content, indirect prompt injection, or an unsafe generated action induces the Agent to invoke one of those tools.
- The Agent reads files unrelated to the creative task, modifies workspace content, or executes a system command.
- Any ac ...[truncated 916 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
exec,read, andwritefrom the Skill because its documented creative-planning workflow only requires text generation. - Maintain one authoritative tool-permission declaration to eliminate inconsistent permission resolution.
- If file access is later required, restrict reads to files explicitly selected by the user and constrain access to a dedicated workspace directory.
- Require explicit user confirmation before every write, overwrite, deletion, or operation affecting files outside generated-output directories.
- Avoid exposing a general-purpose
exectool. If command execution becomes essential, replace it with narrowly scoped operations using fixed executables and argument validation. - Enforce command, path, environment-variable, and network-destination allowlists at the platform level rather than relying on documentation.
- Run the Skill under a sandboxed, low-privilege process without access to unrelated credentials, personal files, or host-level resources.
- Add tests that verify denied access to paths and tools outside the Skill's legitimate operational scope.
- Remove
