T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:26- Finding
Unnecessary Command-Execution Capability Violates Least Privilege
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26–29
Vulnerability Type: Excessive tool permission
Risk Level: MediumVulnerable Code
yaml tools: - read - write - execThe inconsistency is confirmed elsewhere in the same file:
markdown - **Category**: Markdown-only instructions; command-line execution capability is unnecessary.The document also claims command-execution functionality:
markdown - **Command execution**: Execute system commands in a secure sandbox and collect the results.Technical Analysis
The skill requests the
exectool even though it describes itself as a pure Markdown instruction set that does not require command-line execution. Its documented financial calculations and report generation do not establish a legitimate need for arbitrary system-command access.If the hosting agent grants capabilities from this metadata, loading the skill unnecessarily exposes a command-execution channel. This expands the attack surface and violates the principle of least privilege. Untrusted financial data or later task instructions could potentially induce the agent to use this capability outside the skill's legitimate analytical scope.
The reviewed file does not contain a command that directly exploits this access. The issue is therefore an excessive-permission vulnerability rather than evidence of an embedded malicious payload.
Attack Path
- A hosting platform loads
SKILL.mdand grants the tools declared in its metadata. - The skill receives
execaccess despite requiring only document processing and financial analysis. - An attacker supplies crafted task content or financial-document text intended to induce command execution.
- The agent follows the malicious content and invokes
exec. - Commands execute with the filesystem, process, and network permissions available inside the hosting sandbox.
- The resulting damage depends on sandbox isolation and may include unauthorized fi ...[truncated 647 chars]
- A hosting platform loads
- Remediation
View remediation
Remediation Suggestions
- Remove
execfrom the declared tool list. - Retain only narrowly scoped read access needed to process user-provided financial documents.
- Retain write access only if writing reports to files is an explicit requirement; otherwise remove it as well.
- Remove generic command-execution claims from the documentation.
- If a future feature genuinely requires command execution:
- Define the exact permitted commands and arguments.
- Enforce an allowlist in platform code rather than relying on prompt instructions.
- Prohibit shell interpretation and user-controlled command concatenation.
- Run commands in a restricted sandbox with minimal filesystem and network access.
- Apply strict time, CPU, memory, and output limits.
- Log and audit every invocation.
- Replace the generic recommendation to run with administrator privileges when permission errors occur with guidance to verify ownership, select an authorized destination, or contact the responsible administrator.
- Remove
