T08 · Insecure Dependencies
- Location
SKILL.md:252- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 252-255
Vulnerability Type: Unpinned third-party dependency and missing integrity verification
Risk Level: MediumVulnerable Code:
markdown ### Installation Dependencies ```bash pip install ta-libtext ### Technical Analysis The installation instruction retrieves and installs `ta-lib` without specifying an audited version, verifying cryptographic hashes, or constraining the package source. Consequently, the installed artifact can change over time even though the reviewed Skill remains unchanged. Python packages can execute code during installation and subsequently when imported. If the package distribution, package index, maintainer account, or dependency chain is compromised, following this instruction could introduce attacker-controlled code into the user's environment. The finding does not establish that the current `ta-lib` package is malicious; it identifies an unsafe and mutable dependency installation process. ### Attack Path 1. An attacker compromises the package distribution, its maintainer account, the configured package index, or a transitive dependency. 2. A user follows the Skill documentation and runs `pip install ta-lib`. 3. Because no version or artifact hash is required, pip resolves and downloads the attacker-controlled release available through the configured index. 4. Malicious package code executes during installation or later when the package is imported by the technical-analysis workflow. 5. The code runs with the privileges of the user performing the installation or executing the Skill. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the installing user's privileges. Depending on those privileges and the environment, the attacker could access or modify user-readable files, steal environment variables and credentials available to the process, tamper with analysis results ...[truncated 241 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
ta-libto a specifically reviewed version rather than allowing unconstrained resolution. - Generate a locked requirements file containing cryptographic hashes and install it with
pip install --require-hashes -r requirements.txt. - Pin and hash all transitive Python dependencies, not only the direct package.
- Use an explicitly configured, trusted package index or an internally controlled artifact repository.
- Install dependencies inside an isolated virtual environment or container under a non-administrative account.
- Review package provenance, release signatures where available, and dependency vulnerability reports before updating the lock file.
- Document a controlled update process so dependency changes receive security review before deployment.
- Pin
