T08 · Insecure Dependencies
- Location
SKILL.md:108- Finding
Unpinned Third-Party Dependencies Installed at Runtime
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 108–113
Vulnerability Type: Unpinned and unverifiable runtime dependencies
Risk Level: MediumVulnerable Code Snippet:
bash pip install httpx aiohttp beautifulsoup4 lxml requests # Optional: speech-recognition subtitle fallback pip install faster-whisper # Optional: video stream merging # Install ffmpeg on the operating systemTechnical Analysis
The installation instructions use
pip installwithout exact version constraints, package hashes, a lockfile, or a designated trusted package index. Dependency resolution therefore changes over time and may install releases that were not reviewed with this Skill.Python package installation can execute package build or installation logic. If an upstream package or one of its transitive dependencies is compromised, invoking these instructions could execute attacker-controlled code with the privileges of the Agent process. The project contains no dependency manifest or executable implementation that would allow auditors to reproduce and verify the intended dependency graph.
This finding does not establish that any named package is currently malicious. The vulnerability is the absence of controls ensuring that the installed artifacts are the same artifacts that were reviewed and tested.
Attack Path
- An upstream package account, release process, distribution artifact, or transitive dependency is compromised.
- The attacker publishes a malicious version that satisfies the unconstrained dependency request.
- An Agent or user follows the Skill instructions and runs the provided
pip installcommand. - Pip resolves the malicious release because no exact version or hash is required.
- Malicious build, installation, or imported runtime code executes in the Agent environment.
Impact Assessment
Successful exploitation could execute arbitrary code with the operating-system privile ...[truncated 534 chars]
- Remediation
View remediation
Remediation Suggestions
- Provide a reviewed dependency manifest with exact versions for all direct and transitive dependencies.
- Generate and enforce cryptographic hashes, such as with
pip-compile --generate-hashesfollowed bypip install --require-hashes. - Use a lockfile and update dependencies through a controlled review process.
- Explicitly specify an approved HTTPS package index and disable unexpected extra indexes.
- Install dependencies in a dedicated virtual environment or restricted container rather than the Agent's global environment.
- Run automated vulnerability and provenance checks against every locked dependency.
- Document the expected ffmpeg source and version instead of directing users to install an unspecified system package.
