T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 23
Vulnerability Type: Unpinned and unverified third-party dependency
Risk Level: Mediumbash pip install ollama-herd # PyPI: https://pypi.org/project/ollama-herd/Technical Analysis
The installation instructions retrieve and install the latest available
ollama-herdpackage from PyPI without pinning an audited version or verifying an integrity hash. This makes installations non-reproducible and exposes users to supply-chain threats, including compromise of the package publisher, malicious replacement of a future release, or compromise of a transitive dependency.The installed package supplies the
herdandherd-nodeexecutables that users are subsequently instructed to run. Consequently, malicious code introduced into the package or its dependency chain could execute with the privileges of the user performing the installation and operating the services.Attack Path
- An attacker compromises the PyPI package, its publisher account, or a transitive dependency.
- The attacker publishes a malicious release that remains compatible with the unversioned package name.
- A user follows the documented
pip install ollama-herdinstruction. - Pip resolves and installs the attacker-controlled release or dependency.
- The user runs
herdorherd-node, causing the installed malicious code to execute. - The malicious package can access resources available to that user, potentially including local files, model requests, Ollama services, and reachable fleet nodes.
Impact Assessment
Exploitation could result in arbitrary code execution under the installing or service user account. The accessible scope includes that user's files, environment variables, local Ollama traffic, and network resources reachable from the host. If installation or service execution is performed with elevated privileges, the impact would increase accordingly. T ...[truncated 271 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
ollama-herdto a specific version that has undergone security review. - Require cryptographic hashes, such as through a locked requirements file used with
pip install --require-hashes. - Pin and review transitive dependencies to make installations reproducible.
- Document the expected package publisher, source repository, release tag, and package digest so users can verify provenance.
- Recommend installation in a dedicated virtual environment or isolated container under a non-privileged service account.
- Use a controlled internal package mirror or trusted artifact registry for production deployments.
- Establish a dependency-update process that reviews release changes before updating the pinned version.
- Pin
