T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:19- Finding
Excessive Filesystem and Command-Execution Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:19-22
Vulnerability Type: Excessive tool permissions and violation of least privilege
Risk Level: MediumVulnerable Code
yaml tools: - read - exec - writeThe declared capabilities are also described in
SKILL.md:247-249as supporting file reading and writing and system-command execution.Technical Analysis
The Skill declares unrestricted
read,write, andexeccapabilities even though its stated purpose is analysis of stock and cryptocurrency market data. The package contains onlySKILL.mdand provides no implementation demonstrating that unrestricted local filesystem access or shell execution is necessary.No path restrictions, command allowlist, argument validation, execution policy, or enforceable sandbox configuration is supplied. Consequently, a host that grants the declared tools could expose substantially more authority than is required for market-data analysis. This violates the principle of least privilege and enlarges the impact of malicious, compromised, or untrusted instructions processed while the Skill is active.
The declaration alone does not prove that commands are automatically executed or that permissions are granted by every host. Exploitation depends on the host agent honoring these tool declarations and allowing their use without adequate approval or isolation.
Attack Path
- A user or host agent activates the Skill for a financial-analysis task.
- The host grants the declared
read,write, andexectools. - Malicious or untrusted task content induces the agent to use those tools for operations unrelated to financial analysis.
- The agent reads unrelated local files, modifies accessible data, or runs an attacker-selected command.
- The resulting access occurs with the filesystem permissions and operating-system privileges of the host agent process.
Impact Assessment
If the host grant ...[truncated 600 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
execandwriteunless they are demonstrably required for the Skill's core financial-analysis functionality. - Prefer a narrowly scoped network or market-data API tool rather than general-purpose shell execution.
- Restrict reads to files explicitly selected or supplied by the user.
- If export functionality requires writing, confine writes to a dedicated output directory and reject absolute paths, traversal sequences, symbolic-link escapes, and overwriting of existing files by default.
- If command execution is unavoidable, use fixed executable paths and structured argument arrays rather than shell command strings.
- Enforce executable and subcommand allowlists, strict ticker and option validation, resource limits, and a deny-by-default environment.
- Require explicit user confirmation before filesystem modification or command execution.
- Supply and audit the actual implementation so reviewers can verify input validation, sandbox boundaries, and command construction.
- Document the exact permissions needed and ensure the host grants no broader access than those documented permissions.
- Remove
