T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:24
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, line 24 **Vulnerability Type**: Unpinned and unverified third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```powershell pip install ollama-herd ``` ### Technical Analysis The installation instructions retrieve and install the latest available `ollama-herd` package from the user's configured Python package index without specifying a reviewed version, validating cryptographic hashes, or verifying a signed release. Python package installation can execute package-controlled build or installation logic. Consequently, compromise of the upstream package, dependency chain, package index, or configured mirror could cause attacker-controlled code to execute. An unpinned package also allows future releases to change the effective code after this Skill has been reviewed. The package is later invoked through the `herd` and `herd-node` commands and handles network routing and inference traffic, increasing the potential exposure if the installed package is compromised. ### Attack Path 1. An attacker compromises the `ollama-herd` distribution, one of its transitive dependencies, the configured package index, or a package mirror. 2. The attacker publishes or substitutes a malicious package release. 3. A user follows the documented `pip install ollama-herd` instruction. 4. Pip retrieves the attacker-controlled package or dependency because no trusted version or artifact hash is enforced. 5. Malicious code executes during package installation, import, or subsequent invocation of `herd` or `herd-node`. 6. The payload operates with the privileges of the account that performed the installation or launched the installed commands. ### Impact Assessment Successful exploitation can provide arbitrary code execution with the installing or operating user's privileges. Depending on that account's permissions, the attacker could access user-readable files, mod ...[truncated 631 chars]
- Remediation
- ## Remediation Suggestions 1. Pin installation to a specific reviewed release, for example: ```powershell python -m pip install "ollama-herd==<reviewed-version>" ``` 2. Provide a requirements or constraints file containing cryptographic hashes and install with hash enforcement: ```powershell python -m pip install --require-hashes -r requirements.txt ``` 3. Publish and document expected artifact hashes or signed release provenance through a trusted project channel. 4. Explicitly identify the trusted package index and verified publisher. Avoid relying on unknown user-configured mirrors where reproducibility is required. 5. Review and pin transitive dependencies using a lockfile or hash-complete requirements file. 6. Recommend installation in a dedicated virtual environment under a non-administrative account. 7. Advise users not to run pip, `herd`, or `herd-node` from an elevated shell unless a separately documented operation strictly requires it. 8. Establish a controlled update process so new package versions are reviewed before the documented pin is changed.