T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 22
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash pip install ollama-herd # GPU cluster manager from PyPITechnical Analysis
The installation instruction retrieves the latest available
ollama-herdrelease from PyPI without pinning a reviewed version or verifying a cryptographic hash. The installed package supplies the subsequently invokedherdandherd-nodeexecutables, so its installation and execution permit third-party package code to run with the privileges of the current user.This creates a supply-chain risk because the effective code may change after the Skill has been reviewed. A compromised maintainer account, malicious future release, or package-index compromise could cause users following this instruction to install attacker-controlled code. The audit did not find evidence that the currently published package is malicious; the vulnerability is the absence of dependency integrity and version controls.
Attack Path
- An attacker compromises the package publisher, distribution account, or another part of the package-release process.
- The attacker publishes a malicious release under the expected
ollama-herdpackage name. - A user follows the unpinned
pip install ollama-herdinstruction. - Pip retrieves and installs the malicious latest release.
- The user runs
herdorherd-nodeas instructed. - Attacker-controlled package code executes with the user's privileges and can access resources available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the account that installs or runs the package. Depending on that account's permissions, exposed resources may include local files, environment variables, user credentials, network services, GPU-cluster configuration and logs, and cluster nodes reachable from the host.
The instruc ...[truncated 460 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specifically reviewed release:
bash python3 -m pip install "ollama-herd==<reviewed-version>" - Publish and verify SHA-256 hashes for the approved distribution artifacts, preferably through a requirements file using
--require-hashes. - Recommend installation in a dedicated virtual environment rather than the system Python environment.
- Document the trusted package index explicitly and advise users not to use unreviewed mirrors or additional package indexes.
- Review each dependency update before changing the pinned version, including transitive dependencies and package provenance.
- Where practical, use signed releases, attestations, or reproducible build information to strengthen artifact verification.
- Explicitly warn users not to install or run the package with elevated privileges unless a documented feature strictly requires them.
- Pin the dependency to a specifically reviewed release:
