T08 · Insecure Dependencies
- Location
SKILL.md:68- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:68-69
Vulnerability Type: Supply-chain risk from unpinned dependencies
Risk Level: MediumVulnerable Code
bash brew install ffmpeg pip install edge-tts requestsTechnical Analysis
The installation instructions retrieve the latest available versions of
edge-ttsandrequestswithout version constraints, integrity hashes, or a dependency lock file. Consequently, two installations performed at different times can resolve to different package versions and transitive dependency trees.Package installation and subsequent imports execute code supplied by those packages under the privileges of the user running the Skill. If a package account, release pipeline, package artifact, or transitive dependency is compromised, users following these instructions could install attacker-controlled code without any corresponding change to the reviewed Skill repository.
No evidence was found that the Skill intentionally requests a malicious or misspelled package. The issue is the absence of reproducible and integrity-verified dependency resolution.
Attack Path
- An attacker compromises an upstream package, maintainer account, release process, or transitive dependency.
- The attacker publishes a malicious version to the package index.
- A user follows the documented
pip install edge-tts requestscommand. - Pip resolves the unpinned requirement to the malicious release.
- Attacker-controlled package code executes during installation or when the Skill imports and invokes the package.
Impact Assessment
Successful exploitation can execute arbitrary code with the privileges of the user installing or running the Skill. Depending on those privileges, this could expose local files, environment variables such as API credentials, generated media, and network access available to the process. The Skill itself does not request elevated operating-system p ...[truncated 80 chars]
- Remediation
View remediation
Remediation Suggestions
- Provide a reviewed requirements file with exact versions for direct and transitive dependencies.
- Generate and verify package hashes, then require hash checking during installation:
bash pip install --require-hashes -r requirements.txt - Use a dependency-locking tool such as
pip-toolsto produce reproducible dependency resolution. - Pin or otherwise reproducibly install FFmpeg where the deployment environment permits it.
- Add automated dependency vulnerability scanning and controlled update review.
- Install dependencies in an isolated virtual environment under a non-privileged account.
