T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:4- Finding
Excessive Shell and Filesystem Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 4
Vulnerability Type: Excessive tool permissions and violation of least privilege
Risk Level: MediumVulnerable Code Snippet:
yaml --- name: Generate Executive Recruiting Boutique Client Education Handout description: "Create a polished explainer handout with visuals, FAQs, and clear next steps for a executive recruiting firm. Use when handling client education work..." allowed-tools: Bash, Read metadata:Technical Analysis
The Skill is intended to generate and refine an executive recruiting client-education handout. Its documented workflow does not require shell command execution or access to arbitrary local files. Nevertheless, the
allowed-toolsconfiguration grants access to bothBashandRead.Bashcan execute commands with the privileges of the Agent process, whileReadcan access files available to that process. Granting these capabilities without a documented operational requirement violates the principle of least privilege and unnecessarily expands the Skill's attack surface.Although the reviewed file contains no malicious commands, payloads, persistence mechanisms, or explicit data-exfiltration instructions, malicious or attacker-controlled prompt content could potentially influence the Agent into using these unnecessary tools.
Attack Path
- A user or external content supplies attacker-controlled instructions while this Skill is active.
- The content induces the Agent to perform an operation presented as necessary for generating the handout.
- The Agent invokes the unnecessarily authorized
Readtool to access local files orBashto run shell commands. - Commands execute with the Agent process's operating-system privileges, or readable local information is exposed through the generated response.
- The resulting impact depends on the filesystem access, credentials, environment variables, network acce ...[truncated 863 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
BashandReadfromallowed-toolsbecause the documented handout-generation workflow does not require shell or filesystem access. - Authorize only narrowly scoped tools needed to generate text and visuals.
- If file input later becomes necessary, replace unrestricted reading with a scoped mechanism limited to explicitly selected workspace files and approved file types.
- If command execution later becomes essential, use a restricted command allowlist, argument validation, an isolated sandbox, a read-only filesystem where possible, and disabled network access by default.
- Require explicit user approval before accessing local information or executing commands.
- Add automated policy checks that reject Skill manifests requesting tools not justified by their documented workflows.
- Log and review sensitive tool invocations so unexpected file access or command execution can be detected.
- Remove
