T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:13- Finding
Overprivileged Tool Access Violates Least-Privilege Boundaries
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:13-18; related unsafe privilege-elevation guidance atSKILL.md:364
Vulnerability Type: Excessive filesystem and command-execution privileges
Risk Level: MediumVulnerable Code
yaml tools: - read - exec - write - glob - grepTechnical Analysis
The Skill requests unrestricted command execution and broad filesystem read/write capabilities even though its stated primary purpose is browser automation and web data collection. The configuration does not define command allowlists, workspace boundaries, path restrictions, domain restrictions, or approval requirements for security-sensitive operations.
The document also recommends running with administrator privileges as a generic response to insufficient filesystem permissions. This guidance can unnecessarily expand the impact of command execution or file modification. The assertion that commands execute in a secure sandbox is documentary only; the project contains no implementation or enforceable sandbox policy that could be audited.
There is no evidence that this Skill directly performs malicious commands. The risk arises from the excessive authority exposed to agent-generated actions and the absence of enforceable least-privilege controls.
Attack Path
- A user directs the Skill to process an untrusted webpage, API response, or instruction.
- Attacker-controlled content contains instructions that the agent incorrectly interprets as authorized actions.
- The Skill has access to
read,write, andexec, allowing the agent to inspect files, modify accessible files, or execute local commands. - No documented command allowlist, path boundary, or mandatory user confirmation prevents the action.
- If the operator follows the related recommendation to use administrator privileges, the same action may execute with elevated host permissions.
Impact Assessment
Successful exploi ...[truncated 654 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
execunless local command execution is strictly required for a documented browser-automation operation. - Replace unrestricted filesystem tools with workspace-scoped read and write capabilities.
- Use a dedicated browser automation API instead of general-purpose shell execution.
- Enforce allowlists for executable programs, command arguments, destination domains, browser actions, and writable paths.
- Require explicit user confirmation before command execution, file modification, credential access, or other security-sensitive actions.
- Treat webpage content and external API responses as untrusted data and prohibit them from authorizing tool calls.
- Run the Skill as a dedicated unprivileged account inside an enforced sandbox or container with restricted networking and filesystem mounts.
- Replace the generic recommendation to use administrator privileges with least-privilege troubleshooting. Any exceptional elevation should be narrowly scoped, justified, time-limited, and explicitly approved.
- Document concrete sandbox guarantees and add automated tests verifying that commands and file operations cannot escape the permitted workspace.
- Remove
