T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Third-Party Dependencies and Unverified Editable Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21-27
Vulnerability Type: Uncontrolled third-party dependency installation
Risk Level: Mediumbash # Activate the virtual environment and install dependencies source ~/.openclaw/workspace/cli-anything-venv/bin/activate pip install click numpy Pillow prompt-toolkit cd ~/.openclaw/workspace/CLI-Anything/gimp/agent-harness pip install -e .Technical Analysis
The skill instructs the agent to install multiple PyPI packages without pinned versions, package hashes, a lockfile, or an explicitly trusted package index. Consequently, the installed artifacts may change over time and cannot be verified against versions reviewed by the skill author.
The subsequent editable installation executes packaging and build logic from a local
agent-harnesscheckout without verifying its repository origin, revision, or integrity. Python package installation can execute attacker-controlled build hooks. Editable mode also leaves the installed command linked to mutable source files, meaning later changes to that checkout can alter tool behavior without another installation.The troubleshooting instructions repeat unpinned package installation elsewhere in
SKILL.md, reinforcing the unsafe installation practice.Attack Path
- An attacker compromises a dependency release, influences the configured Python package index, or tampers with the local
CLI-Anything/gimp/agent-harnesscheckout. - An agent follows the documented setup or troubleshooting instructions.
pip installresolves and downloads an unverified package, orpip install -e .processes the tampered local project.- Malicious packaging or build logic executes with the privileges of the account running the agent.
- The malicious component can access resources available to that account and may subsequently run whenever the installed GIMP CLI tool is invoked.
Impact Assessment
Succe ...[truncated 525 chars]
- An attacker compromises a dependency release, influences the configured Python package index, or tampers with the local
- Remediation
View remediation
Remediation Suggestions
- Replace ad hoc installation commands with a reviewed lockfile containing exact dependency versions.
- Require package hashes, such as through
pip install --require-hashes -r requirements.txt. - Use an explicitly configured and trusted package index, and prevent fallback to untrusted indexes.
- Verify the local
agent-harnessrepository origin and pin it to a reviewed commit or signed release before installation. - Build an immutable wheel from the verified source and install that artifact instead of using editable mode.
- Perform installation in an isolated, least-privileged environment without access to sensitive credentials.
- Add dependency vulnerability and provenance checks to the release process, and update pinned versions through a controlled review procedure.
