T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:17
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, line 17 **Vulnerability Type**: Unpinned third-party dependency **Risk Level**: Medium ### Vulnerable Code ```bash pip install ollama-herd ``` ### Technical Analysis The installation command resolves and installs the latest version of `ollama-herd` from the Python Package Index without a version constraint or integrity hash. Consequently, the code installed and later executed may differ from the version that existed when this Skill was reviewed. Although the documented PyPI package and GitHub repository are consistent with the Skill's declared identity, the instruction does not protect users against a compromised publisher account, malicious future release, package-index compromise, or unexpected dependency changes. Python package installation may also execute package build logic, while the subsequent `herd` and `herd-node` commands execute installed package code. This is not a confirmed malicious package, but it is a supply-chain weakness that creates a mutable code-execution boundary outside the audited artifact. ### Attack Path 1. An attacker compromises the package publisher account, distribution channel, or a transitive dependency. 2. The attacker publishes a malicious release under the expected package name or introduces malicious dependency resolution behavior. 3. A user follows the documented `pip install ollama-herd` instruction. 4. `pip` resolves the attacker-controlled release because no audited version or hash is required. 5. Malicious code executes during package installation or when the user starts `herd` or `herd-node`. ### Impact Assessment Exploitation could execute arbitrary code with the privileges of the user running `pip`, `herd`, or `herd-node`. This may expose files and credentials accessible to that user, alter local configuration, access network resources, tamper with inference traffic, or affect connected Ollama infrastructure. The instruction does not itself request ele ...[truncated 689 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to a reviewed release: ```bash python3 -m pip install "ollama-herd==1.0.4" ``` 2. Publish a lock file or requirements file containing cryptographic hashes and install with hash enforcement: ```bash python3 -m pip install --require-hashes -r requirements.txt ``` 3. Verify release artifacts through a trusted provenance mechanism, such as signed releases, attestations, or reproducible-build metadata. 4. Pin and audit transitive dependencies rather than constraining only the top-level package. 5. Recommend installation in an isolated virtual environment under an unprivileged account. 6. Avoid `sudo pip install` and explicitly warn users not to run the coordinator or node agent with administrator or root privileges unless a separately documented requirement justifies it. 7. Review and update the pinned version deliberately instead of allowing installation instructions to select future releases automatically.