T08 · Insecure Dependencies
- Location
SKILL.md:125- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:125
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediumbash pip install requestsTechnical Analysis
The installation instructions retrieve
requestswithout specifying a reviewed version or validating an integrity hash. As a result, the installed code depends on whichever release the configured package index resolves at installation time.Although
requestsis a legitimate package and no malicious dependency was found in the repository, this mutable dependency resolution prevents reproducible installation and increases supply-chain exposure. A compromised upstream release, package index, mirror, or dependency resolution path could cause unreviewed code to be installed.Attack Path
- A user follows the installation command in
SKILL.md. pipcontacts the user's configured package index or mirror.- The index resolves a package version that was not fixed or reviewed by this project.
pipdownloads and installs that package and its transitive dependencies.- Malicious package build or installation behavior, if present in the resolved supply chain, executes with the privileges of the user running
pip. - The malicious package can subsequently execute again when the Skill imports
requests.
Impact Assessment
Exploitation could execute arbitrary Python or package-installation code with the privileges of the account performing the installation. The resulting access would generally cover files, credentials, network resources, and processes available to that user. This issue does not independently provide privilege escalation beyond the privileges used to run
pip, but the impact would be greater if installation were performed by an administrator or root account.- A user follows the installation command in
- Remediation
View remediation
Remediation Suggestions
- Declare dependencies in a dedicated requirements or lock file.
- Pin
requestsand all transitive dependencies to versions that have been reviewed and tested. - Record cryptographic hashes and install with hash verification, such as:
bash python -m pip install --require-hashes -r requirements.txt - Use a trusted package index over HTTPS and avoid untrusted mirrors.
- Run dependency installation in an isolated virtual environment without administrative privileges.
- Add automated dependency vulnerability and integrity scanning to the release process.
