T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 35–39
Vulnerability Type: Unpinned and insufficiently verified third-party dependencies
Risk Level: MediumVulnerable Code
markdown Install required dependencies: ```bash pip install requests pandastext ### Technical Analysis The installation command does not specify dependency versions, package hashes, a lockfile, or a trusted package repository. Consequently, the packages installed can change between executions even if the audited skill remains unchanged. Although `requests` and `pandas` are established projects, resolving mutable package names without integrity verification leaves installation dependent on the current contents of the configured Python package index. The risk can become exploitable if an upstream release, dependency, configured mirror, or package index is compromised. It can also cause unreviewed breaking or vulnerable versions to enter the environment. ### Attack Path 1. An attacker compromises an upstream package release, transitive dependency, package repository, or package mirror used by the victim. 2. The attacker publishes or substitutes a malicious version under a dependency name resolved by the documented command. 3. A user follows the skill's prerequisite instructions and runs `pip install requests pandas`. 4. Because no versions or hashes are enforced, `pip` resolves and installs the attacker-controlled artifact. 5. Malicious package installation or import-time logic executes in the user's Python environment when installed or subsequently imported. This path requires compromise or manipulation of the dependency supply chain; the audited artifact does not itself contain a malicious package or remote payload. ### Impact Assessment Malicious dependency code would generally execute with the privileges of the account running `pip` or the scanner. Potential scope includes: - Reading or modifying files a ...[truncated 615 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the direct installation command with a reviewed and version-controlled dependency file containing exact versions.
- Generate and enforce cryptographic hashes, for example:
bash python -m pip install --require-hashes -r requirements.txt - Maintain dependencies through a lockfile generated by a tool such as
pip-tools, Poetry, or uv. - Explicitly document the trusted package index and prevent fallback to untrusted extra indexes.
- Install dependencies inside a dedicated virtual environment rather than a shared or system Python environment.
- Avoid running package installation as
rootor with administrator privileges. - Regularly scan locked dependencies for known vulnerabilities and review updates before changing pinned versions.
- Include the missing implementation files in the distributable artifact so dependency usage and runtime behavior can be independently audited.
