T08 · Insecure Dependencies
- Location
SKILL.md:46- Finding
Unpinned Python Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:46,scripts/mimo_tts.py:8,scripts/mimo_tts_voiceclone.py:8,scripts/mimo_tts_voicedesign.py:8
Vulnerability Type: Unpinned third-party dependency
Risk Level: LowVulnerable code snippets:
markdown | `openai` | `pip install openai` | Yes |python # Present in each Python script: Requires: pip install openai export MIMO_API_KEY=...Technical Analysis
The installation instructions request the latest available
openaipackage without pinning a reviewed version or verifying package hashes. The Skill does not include a lock file or hash-validated requirements file.Package installation can execute package-controlled build and installation logic. Consequently, the code installed in the future may differ from the dependency version reviewed alongside this Skill. This creates exposure to compromised releases, malicious transitive dependencies, and unexpected compatibility or security regressions.
The instruction is documentation rather than automatic package installation, and it uses the expected package name rather than an evident typosquat. Therefore, this is a supply-chain hardening weakness rather than evidence that the project intentionally installs a malicious dependency.
Attack Path
- An attacker compromises a future release of the referenced package or one of its unpinned transitive dependencies.
- A user follows the documented
pip install openaiinstruction. - The package manager resolves and downloads the compromised version because no approved version or hash is enforced.
- Malicious installation or runtime code executes with the privileges of the user running
pip. - That code may access data available to the process, potentially including
MIMO_API_KEY, generated audio, and other user-accessible files.
Impact Assessment
Successful exploitation would execute dependency-controlled cod ...[truncated 278 chars]
- Remediation
View remediation
Remediation Suggestions
-
Add a reviewed dependency file with an exact version, for example:
text openai==<reviewed-version> -
Generate and enforce cryptographic hashes for the package and all transitive dependencies, such as with
pip-toolsand:bash python3 -m pip install --require-hashes -r requirements.txt -
Use a dedicated virtual environment rather than installing into a system or privileged Python environment.
-
Document the supported Python and dependency versions.
-
Periodically update the pinned version through a controlled review and vulnerability-scanning process.
-
Avoid running package installation as
rootor withsudo.
-
