T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Third-Party Dependency Allows Unreviewed Package Changes
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20–27
Vulnerability Type: Unpinned third-party dependency
Risk Level: LowVulnerable Code
json { "id": "pip-deps", "kind": "python", "package": "httpx", "label": "Install Python dependencies" }Technical Analysis
The installation configuration specifies
httpxwithout an exact version constraint or an integrity hash. Dependency resolution can therefore select a different package release each time the Skill is installed.This does not establish that the current
httpxpackage is malicious. However, it creates a supply-chain exposure because future releases are incorporated without review. A compromised package publisher, package registry, dependency-resolution source, or newly released vulnerable version could cause unsafe code to be installed.Python package installation may execute package build hooks and other installation-time code. Consequently, a malicious release selected by the unpinned dependency could execute code in the environment performing the installation.
Attack Path
- An attacker compromises the relevant package publication channel, registry resolution path, or a future package release.
- The attacker publishes or causes resolution to select a malicious or compromised version of
httpx. - A user installs the Skill after that version becomes available.
- The installer resolves
"package": "httpx"to the affected release because no exact version or hash is enforced. - Malicious installation hooks or imported package code execute with the privileges of the installation or runtime process.
Impact Assessment
Successful exploitation could execute arbitrary code with the privileges of the account or service installing or running the Skill. Depending on those privileges, the compromised dependency could access environment variables such as
EM_API_KEY, read or modify files available to ...[truncated 309 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
httpxto an exact, reviewed version rather than allowing unrestricted resolution. - Maintain dependencies in a lock file generated from a trusted environment.
- Require cryptographic hashes for downloaded distributions, such as through a hash-locked requirements file.
- Install packages only from an explicitly configured, trusted package index.
- Regularly scan the pinned version and its transitive dependencies for disclosed vulnerabilities.
- Test and review dependency upgrades before changing the pinned version.
- Perform installation in a least-privileged, isolated environment without unnecessary credentials or host filesystem access.
- Pin
