T08 · Insecure Dependencies
- Location
SKILL.md:275- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 275
Vulnerability Type: Unpinned and unverifiable third-party dependencies
Risk Level: MediumVulnerable Code Snippet:
markdown - Dependency installation command: `pip install numpy pandas scikit-learn tensorflow`Technical Analysis
The installation command does not constrain package versions, verify package hashes, use a lockfile, or specify an approved package repository. Consequently, the packages and their transitive dependencies can change between installations without any modification to the reviewed Skill.
Python package installation can execute package build and installation logic. If a package release, transitive dependency, or configured package index is compromised, following this instruction may execute attacker-controlled code with the privileges of the user running
pip.The named packages are legitimate and there is no evidence that they are currently malicious. The vulnerability arises from the unsafe, mutable dependency-resolution process rather than from a confirmed malicious package.
Attack Path
- A user or Agent follows the dependency installation instruction.
pipqueries the environment's configured package indexes and resolves the latest compatible versions.- A compromised package release, transitive dependency, or malicious package index supplies attacker-controlled package content.
- Package build or installation hooks execute attacker-controlled code.
- The code gains the permissions of the account running
pip; if installation is combined with the document's administrator-execution advice, the impact may extend to elevated system privileges.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. This may expose files, environment variables, configured API keys, financial datasets, and other resources available to that account. ...[truncated 238 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the inline installation command with a reviewed dependency manifest containing exact versions.
- Generate and enforce cryptographic hashes, for example by using a hash-locked requirements file and
pip install --require-hashes. - Pin all transitive dependencies through a reproducible lockfile.
- Explicitly require installation from an approved package repository and reject untrusted extra indexes.
- Require installation in a dedicated, unprivileged virtual environment or container.
- Add automated dependency vulnerability and provenance scanning.
- Document a controlled process for reviewing and updating pinned versions.
