T08 · Insecure Dependencies
- Location
docs/INSTALL.md:46- Finding
Unpinned Third-Party Dependencies Permit Supply-Chain Drift
- Content
View full analysis
Vulnerability Details
File Location:
docs/INSTALL.md:46-48
Vulnerability Type: Unpinned third-party package installation
Risk Level: MediumVulnerable Code
bash pip3 install edge-tts aiohttp requestsTechnical Analysis
The installation instructions retrieve the latest available versions of
edge-tts,aiohttp, andrequestswithout version constraints or cryptographic hashes. Consequently, the code installed by users can differ from the code available when the Skill was audited.Python packages may execute installation or build logic during installation, and their imported modules execute with the privileges of the user running the Skill. If a dependency or one of its transitive dependencies is compromised, a user following these instructions may install and execute malicious code.
This is a supply-chain hardening issue rather than evidence that the currently named packages are malicious.
Attack Path
- An attacker compromises a listed package, a transitive dependency, or the corresponding package-distribution account.
- The attacker publishes a malicious release under the legitimate package name.
- A user follows
docs/INSTALL.mdand runs the unpinnedpip3 installcommand. - Package resolution selects the attacker-controlled release.
- Malicious installation or runtime code executes with the privileges of the installing user.
- The malicious package can access files, network resources, and credentials available to that user.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user installing or running the Skill. The affected scope may include the user's files, environment variables, accessible credentials, network access, and generated media. If the installation command is run from a privileged environment, the impact would increase accordingly.
- Remediation
View remediation
Remediation Suggestions
-
Define reviewed, exact dependency versions in a dedicated requirements file:
text edge-tts==REVIEWED_VERSION aiohttp==REVIEWED_VERSION requests==REVIEWED_VERSION -
Generate and verify cryptographic hashes for every direct and transitive dependency.
-
Install packages with hash enforcement:
bash python3 -m pip install --require-hashes -r requirements.txt -
Use a lock-file tool such as
pip-toolsto resolve and pin the full transitive dependency graph. -
Periodically update dependencies through a controlled review process that includes vulnerability scanning and regression testing.
-
Recommend installation in a dedicated virtual environment under a non-privileged account.
-
