T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:27- Finding
Excessive Tool Permissions Violate Least-Privilege Requirements
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27–31
Vulnerability Type: Excessive filesystem and command-execution permissions
Risk Level: Mediumyaml tools: - read - exec - write - globTechnical Analysis
The Skill requests
read,exec,write, andglobcapabilities even though its documented purpose is to provide a methodology for statistical analysis and reporting. The documented workflow does not require arbitrary command execution, unrestricted file modification, or filesystem discovery.This configuration violates the principle of least privilege. In an agent environment where declared tools are granted without additional isolation, untrusted analysis input could influence the agent to invoke these capabilities outside the legitimate scope of the Skill. The reviewed file does not contain instructions that directly perform such operations; therefore, the issue is excessive capability exposure rather than evidence of an intentionally malicious payload.
Attack Path
- The Skill is loaded with all four declared tools available.
- An attacker supplies a dataset, filename, or analysis request containing adversarial instructions.
- The agent interprets those instructions as part of the requested analytical workflow.
- The attacker induces the agent to use
globandreadto discover and inspect files unrelated to the supplied dataset. - The attacker may then induce the agent to use
writeto modify accessible files orexecto run commands under the agent process's operating-system identity. - Any resulting access remains bounded by the host permissions, sandbox, approval controls, and tool restrictions enforced by the agent platform.
Impact Assessment
Successful exploitation could expose files readable by the agent process, modify files writable by that process, or execute commands with the process's existing operating-system privileges. Potentia ...[truncated 404 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
exec,write, andglobbecause they are not necessary for the documented statistical guidance workflow. - Retain
readonly if the Skill must analyze local datasets; otherwise, remove all tool permissions and accept data directly through user input. - If local file access is required, restrict reading to files explicitly selected by the user and to a dedicated workspace or dataset directory.
- Require explicit user confirmation before accessing any file not directly supplied with the analysis request.
- If command execution is introduced in a future version, use a narrowly scoped allowlist, prohibit shell interpolation of untrusted input, execute inside a sandbox, and require approval for every command.
- Restrict write access to a dedicated output directory, use non-overwriting file creation where possible, and prevent modification of source code, configuration, credentials, and system paths.
- Treat dataset contents and callback-related values as untrusted data rather than executable instructions.
- Remove
