T08 · Insecure Dependencies
- Location
engines/__init__.py:104- Finding
Automatic Installation of Unpinned Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
requirements.txt:1-3;engines/__init__.py:104-115
Vulnerability Type: Supply-chain exposure through unpinned automatic dependency installation
Risk Level: MediumVulnerable Code
requirements.txt:1-3text faster-whisper openai-whisper ffmpeg-pythonengines/__init__.py:104-115python # Step 3: Install requirements.txt print("[Setup] Installing dependencies...") try: result = subprocess.run( [str(pip_path), "install", "-r", str(requirements_path)], capture_output=True, text=True, timeout=600, ) if result.returncode != 0: raise RuntimeError(f"Failed to install requirements: {result.stderr}") print("[Setup] Dependencies installed")Technical Analysis
When neither ASR engine can be imported, the Skill automatically invokes pip to install dependencies from
requirements.txt. The dependencies have no fixed versions or cryptographic hashes. Consequently, the package versions and transitive dependency graph can change without any modification to the reviewed Skill.Python packages may execute code during installation, import, or normal runtime. Automatic installation therefore extends trust from the audited project to the latest package artifacts selected by the configured package index. A compromised future release, compromised transitive dependency, or unsafe package-index configuration could result in arbitrary code execution.
The environment readiness check also only verifies that
pip listreturns a nonempty package list. It does not verify the identities, versions, hashes, or integrity of the required packages.Attack Path
- An attacker compromises a direct or transitive dependency distributed through the configured Python package index, or influences the package source used by pip.
- A user invokes the subtitle Skill on a system where the supported ...[truncated 889 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin exact versions for all direct dependencies and maintain a reviewed lock file containing the complete transitive dependency graph.
- Record cryptographic hashes for every accepted distribution and install with
pip install --require-hashes. - Use a controlled package repository or allowlisted internal mirror rather than relying implicitly on the user's package-index configuration.
- Do not install packages automatically during normal subtitle processing. Require an explicit, documented setup action and informed user approval.
- Verify required package names, versions, and hashes instead of treating any nonempty virtual environment as valid.
- Apply restrictive permissions to
~/.whisper-venvand reject environments owned by or writable by another user. - Run dependency installation and model processing in an isolated, least-privileged environment where practical.
- Add automated dependency vulnerability and provenance scanning to the release process.
