T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Execution of an Unverified Out-of-Package Installer
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31–33
Vulnerability Type: Insecure third-party dependency installation
Risk Level: MediumVulnerable Code
markdown This skill requires the banana extension to be installed: ```bash ./extensions/banana/install.shtext The same command is recommended again in the error-handling guidance at lines 142 and 146–147: ```markdown | MCP not configured | Run `./extensions/banana/install.sh` | | MCP unavailable | Configure MCP with `./extensions/banana/install.sh`; seo-geo-skill does not vendor a local generation fallback script | | Extension not installed | Show install instructions: `./extensions/banana/install.sh` |Technical Analysis
The skill directs the user or executing agent to run a relative installer that is not included in the audited project. Consequently, this artifact provides no way to verify the script's contents, provenance, integrity, version, or resulting permissions.
The relative path is resolved according to the current working directory rather than a verified package root. If an attacker can create or replace
./extensions/banana/install.shin that execution context, the documented command will execute attacker-controlled code while appearing to be the skill's legitimate installation procedure.This creates a supply-chain trust gap: the skill depends on an external component but does not pin a release, verify a checksum or signature, or validate that the resolved installer belongs to the intended Banana extension.
Attack Path
- An attacker gains write access to the workspace or otherwise controls the current working directory used when the skill runs.
- The attacker creates or replaces
./extensions/banana/install.shwith a malicious script. - The Banana MCP tools are unavailable, causing the skill to present its prerequisite or error-handling instructions.
- The user or agent follows the documented command without verifying the script's origin ...[truncated 907 chars]
- Remediation
View remediation
Remediation Suggestions
- Bundle the required installer within the reviewed package, or reference a specific official release from a trusted source.
- Pin the dependency to an immutable version or commit rather than relying on an unspecified external installation.
- Publish and verify a cryptographic checksum or signed release before execution.
- Resolve the installer relative to a trusted, canonical package root instead of the current working directory.
- Before running any installer, display its resolved absolute path and provenance and require explicit user approval.
- Validate ownership and permissions and reject scripts located in writable or unexpected directories.
- Document exactly what the installer changes, which packages it installs, and which credentials or permissions it requires.
- Apply the corrected installation procedure consistently to the repeated guidance at
SKILL.md:142andSKILL.md:146–147.
