T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:29
Vulnerability Type: Unpinned dependency installation
Risk Level: MediumVulnerable Code Snippet:
bash pip install faster-whisperTechnical Analysis
The installation command does not pin
faster-whisperto a reviewed version and does not verify package integrity using cryptographic hashes. It therefore installs whichever release and transitive dependencies the package index resolves at installation time.This makes the effective dependency code mutable after the Skill has been audited. If the upstream package, maintainer account, distribution channel, or a transitive dependency is compromised, a user following the documented command may install attacker-controlled code. Python packages may execute build hooks during installation and arbitrary code when subsequently imported by the audio workflow.
The issue is limited to the documented dependency installation process. The audited Skill does not itself retrieve and execute a remote script, and exploitation requires the user to follow the installation instruction while a malicious or compromised package version is available.
Attack Path
- An attacker compromises the upstream package, its publishing credentials, or one of its unresolved transitive dependencies.
- The attacker publishes a malicious release that remains compatible with the unpinned package name.
- A user follows the Skill documentation and runs
pip install faster-whisper. - Package resolution selects the malicious release or dependency because no approved version or hash is enforced.
- Attacker-controlled code executes through package installation hooks or when
video_to_screenplay.pyimportsfaster_whisperfor the--audioworkflow. - The malicious code operates with the privileges of the user running
pipor the Skill.
Impact Assessment
Successful exploitation could provide arbitrary code execution w ...[truncated 558 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
faster-whisperand every transitive dependency to reviewed versions in a lock file. - Record and enforce package hashes using a requirements file, for example:
bash pip install --require-hashes -r requirements.txt - Generate the lock file from a trusted package index and review dependency updates before changing pinned versions or hashes.
- Explicitly specify the official package index and disable unintended additional indexes to reduce dependency-confusion exposure.
- Install dependencies inside an isolated virtual environment with no administrative privileges.
- Consider using pre-reviewed wheels and disabling source builds where operationally feasible to reduce exposure to build-time execution.
- Pin
