T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:29
- Finding
- Unpinned Third-Party Package Installation and Execution<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 29–31 **Vulnerability Type**: Unpinned and externally managed software dependency **Risk Level**: Medium ### Vulnerable Code ```bash pip install ollama-herd # PyPI: https://pypi.org/project/ollama-herd/ herd # start the router (port 11435) herd-node # run on each device — finds the router automatically ``` ### Technical Analysis The installation instructions retrieve the latest available `ollama-herd` package from PyPI without specifying a reviewed version or validating an integrity hash. The instructions then execute the package-provided `herd` and `herd-node` entry points. Because the installed implementation is not included in this project, its effective behavior cannot be verified from the audited artifact. The downloaded content can also change after this Skill has been reviewed. A compromised package publisher account, package-index compromise, or unexpectedly changed future release could therefore introduce arbitrary code. This is not evidence that the current `ollama-herd` package is malicious. The risk arises from trusting mutable, unpinned third-party code and immediately executing it. ### Attack Path 1. An attacker compromises the upstream package, its publisher account, or its release process. 2. The attacker publishes a modified `ollama-herd` release to the package source used by `pip`. 3. A user follows the documented command `pip install ollama-herd`. 4. Because no version or hash is specified, `pip` retrieves the attacker-controlled or unexpectedly modified release. 5. The user executes `herd` or `herd-node`, causing package-controlled code to run under the user's account. ### Impact Assessment A compromised dependency would execute with the privileges of the user running the installation and service commands. Depending on those privileges and the dependency's implementation, this could permit: - Reading or modifying fil ...[truncated 585 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin `ollama-herd` to a specifically reviewed version rather than installing the latest available release: ```bash python3 -m pip install "ollama-herd==<reviewed-version>" ``` 2. Distribute a locked requirements file containing cryptographic hashes and install it with hash enforcement: ```bash python3 -m pip install --require-hashes -r requirements.txt ``` 3. Install the package in a dedicated virtual environment or another appropriately isolated runtime instead of the system Python environment. 4. Verify release provenance through trusted package metadata, signed releases, or a controlled internal package mirror. 5. Review the installed package and its transitive dependencies before updating the pinned version. 6. Run `herd` and `herd-node` as a dedicated, non-administrative account with only the filesystem and network permissions required for fleet routing. 7. Document the expected network bindings and recommend restricting the service to loopback or trusted interfaces unless remote fleet access is explicitly required. ]]>