T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 32
Vulnerability Type: Unpinned package installation from a mutable public package repository
Risk Level: Mediumbash pip install edge-ttsTechnical Analysis
The documented installation command retrieves the latest available version of
edge-ttsand its transitive dependencies from the package index. The project provides no version constraint, cryptographic hash verification, lockfile, or reviewed dependency manifest. As a result, the effective code installed by this command can change after the Skill has been audited.This creates a supply-chain exposure if a future package release or transitive dependency is compromised. The audit found no evidence that the currently published package is malicious; the risk arises from the mutable and unverified installation procedure.
Attack Path
- An attacker compromises the referenced package, one of its transitive dependencies, or the associated package publication account.
- The attacker publishes a malicious release that satisfies the unrestricted installation request.
- A user or Agent follows the Skill documentation and executes
pip install edge-tts. - Pip downloads and installs the attacker-controlled release or dependency.
- Malicious code executes during installation or when the package is subsequently imported or invoked.
Impact Assessment
Successful exploitation could execute arbitrary code with the privileges of the user running pip or the TTS workflow. Depending on those privileges and the environment, the compromised package could access project files, user-readable credentials, environment variables, and network resources, or modify files available to that account. The issue does not independently provide privilege escalation beyond the invoking account.
- Remediation
View remediation
Remediation Suggestions
-
Pin
edge-ttsand every transitive dependency to reviewed versions. -
Store dependencies in a lockfile or hash-locked requirements file.
-
Require cryptographic hashes during installation:
bash python3 -m pip install --require-hashes -r requirements.txt -
Install dependencies in a dedicated, non-privileged virtual environment rather than globally or as an administrative user.
-
Review dependency updates before changing pinned versions and use automated vulnerability and provenance scanning.
-
Include the reviewed dependency manifest in the project so installation behavior is reproducible.
-
