T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:6- Finding
Excessive and Inconsistent Tool Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 6-22
Vulnerability Type: Excessive filesystem and command-execution permissions
Risk Level: MediumVulnerable Code
yaml allowed-tools: read execyaml tools: - exec - read - writeTechnical Analysis
The Skill contains two inconsistent tool-permission declarations. The
allowed-toolsfield grantsreadandexec, while the latertoolsfield additionally requestswrite.Filesystem write access is not necessary for the documented search operation. The Skill also describes generic file processing and system-command execution at lines 383-385, extending its requested capabilities beyond querying a SearXNG endpoint.
If a host platform treats the broader
toolsfield as authoritative, the Skill may receive filesystem modification privileges that are not required for its stated purpose. Broadexecaccess also lacks an enforceable command allowlist; the security guidance at line 352 recommends a whitelist but does not define or implement one.No evidence shows that the Skill currently uses these permissions maliciously. The vulnerability is the unnecessary and ambiguous privilege request, which breaks the principle of least privilege and increases the impact of prompt injection or untrusted search content.
Attack Path
- An Agent loads the Skill and parses its tool declarations.
- The hosting platform resolves the conflicting declarations by granting the broader
exec,read, andwriteset. - The Agent processes attacker-controlled search content or a malicious instruction embedded in external content.
- That content induces the Agent to invoke the broadly available command or write tools.
- Commands execute or files are modified within the operating-system permissions of the Agent process.
Impact Assessment
A successful exploitation could permit modification of files accessible to the A ...[truncated 291 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
writebecause the documented search workflow does not require filesystem modification. - Replace the conflicting declarations with one authoritative tool-permission list.
- Avoid granting unrestricted shell execution. Expose a dedicated search API tool instead of a general-purpose
execcapability. - If command execution is unavoidable, enforce a host-level allowlist containing only fixed commands and arguments.
- Run all commands in a restricted sandbox with minimal filesystem access, no elevated privileges, and constrained network access.
- Treat all search results and remote content as untrusted data and prevent them from supplying executable Agent instructions.
- Remove
