T08 · Insecure Dependencies
- Location
install.sh:22- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
install.sh:22-24
Additional Locations:SKILL.md:25-27,docs/README.md:49-52,skill.json:27-33
Vulnerability Type: Unpinned dependency installation and supply-chain exposure
Risk Level: MediumVulnerable Code
bash # 安装依赖 echo "📦 安装 Python 依赖..." pip3 install watchdogThe same unrestricted package installation is declared in
skill.json:json "dependencies": [ "watchdog" ], "commands": [ "pip3 install watchdog", "chmod +x scripts/*.py scripts/*.sh" ]Technical Analysis
The installer obtains the latest version of
watchdogresolved by the user's configured Python package index. It does not specify an audited version, verify an integrity hash, use a lock file, or isolate the dependency in a dedicated virtual environment.The dependency is legitimate and necessary for the real-time watcher, and no dependency-confusion or typosquatting package was identified in the supplied project. Nevertheless, unrestricted dependency resolution means the code installed today may differ from the code reviewed or installed later. A compromised upstream release, compromised package index, maliciously configured index, or incompatible future release could introduce arbitrary installation-time or runtime behavior.
Because
pip3installs packages using the privileges of the invoking user, the resulting exposure depends on how the installer is launched. Normal use exposes the OpenClaw user's account and data; running the installer with elevated privileges would unnecessarily increase the potential impact.Attack Path
- An attacker compromises the upstream package, its maintainer account, a configured package index, or the dependency delivery path.
- A malicious version becomes the version selected by the unrestricted
pip3 install watchdogcommand. - The user executes
install.sh. - Pip retrieves and installs the se ...[truncated 837 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin
watchdogto a reviewed version rather than resolving the newest release:bash python3 -m pip install 'watchdog==<reviewed-version>' -
Maintain a requirements lock file containing integrity hashes and install with hash enforcement:
bash python3 -m pip install --require-hashes -r requirements.txt -
Install dependencies into a dedicated virtual environment rather than modifying the user's global Python environment.
-
Document that the installer must not be run with
sudoor as root. -
Keep the pinned dependency under periodic security review and update it through an explicit, tested release process.
-
Ensure
SKILL.md,docs/README.md, andskill.jsonall use the same pinned and verified dependency specification.
-
