T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:23- Finding
Excessive and Underspecified Tool Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23-26
Vulnerability Type: Excessive tool permissions violating least-privilege principles
Risk Level: Mediumyaml tools: - read - exec - writeTechnical Analysis
The skill declares general-purpose file-reading, file-writing, and command-execution capabilities. Its stated purpose is financial market-data retrieval and analysis, which does not inherently require unrestricted access to local files or arbitrary system commands.
The document does not define path restrictions, a command allowlist, cache-directory boundaries, shell-input validation, user-approval requirements, or an enforceable sandbox policy. In particular, the
execpermission is not justified by a concrete financial-data operation. If the hosting agent grants these tools according to the manifest, the skill receives capabilities beyond its documented functional requirements.The project contains no executable scripts and no explicit malicious command. Exploitation therefore depends on the hosting agent exposing the declared tools and on attacker-controlled prompts or untrusted external content influencing tool use.
Attack Path
- A user or platform loads the skill and grants the declared
read,write, andexectools. - An attacker supplies a crafted financial request, or untrusted provider content introduces instructions that influence the agent.
- The agent interprets those instructions as requiring local file access or command execution.
- Because the skill defines no path, command, or argument restrictions, the agent may read unrelated files, modify local data, or execute commands outside the legitimate market-data workflow.
- The resulting access can affect confidentiality or integrity within the permissions and sandbox boundaries of the hosting agent.
Impact Assessment
Successful exploitation could permit:
- Reading files accessible to the agen ...[truncated 635 chars]
- A user or platform loads the skill and grants the declared
- Remediation
View remediation
Remediation Suggestions
- Remove
execunless a specific, documented operation strictly requires command execution. - Replace general-purpose tools with narrowly scoped financial-data API tools where the platform supports them.
- If caching is required, restrict
readandwriteto a dedicated cache directory and prevent path traversal, symlink escapes, and access to unrelated files. - Define approved data providers, destination domains, request methods, timeouts, response-size limits, and provider-fallback behavior.
- Validate financial symbols and intervals against strict allowlists before using them in file paths, URLs, or command arguments.
- Prohibit direct shell interpolation of user-controlled or provider-controlled values. If command execution is unavoidable, use fixed executables and structured argument arrays.
- Require explicit user confirmation before exceptional file operations or system-command execution.
- Document and enforce sandbox boundaries, minimum filesystem permissions, and denial of access to credentials, environment secrets, and system directories.
- Add tests confirming that financial requests cannot trigger unrelated file access or arbitrary command execution.
- Remove
