T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15 and 55
Vulnerability Type: Supply-chain exposure through an unpinned Python dependency
Risk Level: MediumVulnerable Code
Installation metadata at line 15:
json { "id": "faster-whisper-venv", "kind": "bash", "label": "Install faster-whisper in venv", "command": "python3 -m venv ~/.openclaw/workspace/voice-messages && ~/.openclaw/workspace/voice-messages/bin/pip install faster-whisper" }The installation instructions repeat the unsafe command at line 55:
bash ~/.openclaw/workspace/voice-messages/bin/pip install faster-whisperTechnical Analysis
The Skill installs
faster-whisperwithout a fixed version, dependency lockfile, or package hashes. Pip therefore resolves the latest package and compatible transitive dependencies available from its configured package index at installation time.This makes the executed dependency set mutable after the Skill has been reviewed. A compromised future release, compromised package-index account, or malicious transitive dependency could introduce attacker-controlled code. A virtual environment limits package isolation but does not sandbox execution or restrict access to resources available to the OpenClaw user.
Attack Path
- An attacker compromises the
faster-whisperdistribution channel, a maintainer account, or one of its unresolved transitive dependencies. - The attacker publishes a malicious release that satisfies pip's unconstrained resolution.
- A user installs the Skill or follows its installation instructions.
- Pip downloads and installs the malicious package because no reviewed version or cryptographic hash is required.
- Attacker-controlled code runs during package installation, Python import, model initialization, or subsequent audio transcription.
- The malicious code operates with the permissions of the user running OpenClaw.
Impac
...[truncated 564 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin
faster-whisperto a specifically reviewed version rather than installing an unconstrained latest release. -
Resolve and pin all transitive dependencies in a lockfile generated in a controlled environment.
-
Record cryptographic hashes for every package artifact and install with hash enforcement, for example:
bash ~/.openclaw/workspace/voice-messages/bin/pip install \ --require-hashes \ -r requirements.lock -
Prefer an explicitly trusted package index and disable unintended fallback indexes to reduce dependency-confusion exposure.
-
Review dependency updates and regenerate the lockfile intentionally rather than resolving new releases during every installation.
-
Run transcription with least privilege and restrict the OpenClaw service account's access to credentials, configuration files, and unrelated user data.
-
Apply the same secured installation command in both the executable metadata and the documentation so users cannot inadvertently follow the unsafe variant.
-
