T08 · Insecure Dependencies
- Location
SKILL.md:68- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:68-72
Vulnerability Type: Unpinned runtime dependency
Risk Level: MediumVulnerable Code Snippet:
bash pip3 install requests python3 "$SKILL_PATH/scripts/imagegen.py" init --skill-name gpt-image-2-ad-image python3 "$SKILL_PATH/scripts/imagegen.py" task --task-id <taskId>Technical Analysis
The documented installation command retrieves
requestswithout specifying an audited version, dependency lock file, package hash, or trusted package index. Consequently, the exact code installed is mutable and may differ between installations performed at different times.This creates supply-chain exposure if the package registry, a transitive dependency, the selected package release, or the package-resolution path is compromised. It also permits future incompatible releases to change the script's network behavior without a corresponding review of this project.
The issue does not establish that the current
requestspackage is malicious. The risk arises because the instructions trust mutable external package contents at installation time without reproducibility or integrity verification.Attack Path
- An attacker compromises a future
requestsrelease, one of its resolved dependencies, or the package distribution channel used by the victim. - A user follows the documented
pip3 install requestscommand. pipresolves and installs the attacker-controlled or compromised release because no version or hash constraint is present.- Malicious package code executes during installation or when
scripts/imagegen.pyimportsrequests. - The malicious code operates with the privileges of the user running
pipor the skill and may access that user's files, environment variables, and outbound network connection.
Impact Assessment
Successful exploitation can obtain the privileges of the account that installs or runs the skill. With ...[truncated 500 chars]
- An attacker compromises a future
- Remediation
View remediation
Remediation Suggestions
-
Replace the unconstrained installation command with an audited, exact version constraint, for example through a dedicated
requirements.txt. -
Generate and verify cryptographic hashes for the package and all transitive dependencies, using an installation command such as:
bash python3 -m pip install --require-hashes -r requirements.txt -
Maintain a lock file that records the complete dependency graph for each supported Python environment.
-
Configure an approved HTTPS package index rather than relying on an unspecified local or global
pipconfiguration. -
Review dependency updates before changing pinned versions, including release provenance, vulnerability advisories, and transitive dependency changes.
-
Recommend installation in an isolated virtual environment with ordinary user privileges, and explicitly advise against running
pipas root.
-
