T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:29
- Finding
- Unpinned Third-Party Package Installation<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, line 29 **Vulnerability Type**: Unpinned package dependency and supply-chain exposure **Risk Level**: Medium ### Vulnerable Code ```bash pip install ollama-herd # PyPI: https://pypi.org/project/ollama-herd/ ``` ### Technical Analysis The installation instruction retrieves the current package release associated with `ollama-herd` from PyPI without specifying an exact version or validating an integrity hash. Python package installation can execute package-controlled build or installation logic with the privileges of the invoking user. The project does not include a dependency lockfile, constraints file, package hashes, vendored source, or other mechanism that binds installation to a reviewed artifact. Consequently, the effective code installed by this instruction can change after this Skill has been audited. This does not establish that the named package is malicious. The vulnerability is the absence of dependency pinning and integrity verification, which exposes users to package-repository compromise, publisher-account compromise, malicious future releases, or an unintended incompatible release. ### Attack Path 1. An attacker compromises the package publisher account, package repository, release workflow, or another component capable of publishing a new `ollama-herd` release. 2. The attacker publishes a release containing malicious build, installation, or runtime code. 3. A user follows the documented `pip install ollama-herd` instruction after the malicious release becomes the version selected by pip. 4. Pip downloads the mutable release without checking it against a project-supplied version and hash. 5. Package-controlled code executes during installation or when the installed `herd` or `herd-node` command is subsequently launched. 6. The payload operates with the permissions of the user who performed the installation or launched the package. ### Impact Assessment Successful exploi ...[truncated 1038 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the dependency to a specifically reviewed version: ```bash python3 -m pip install "ollama-herd==<reviewed-version>" ``` 2. Publish a requirements or constraints file containing cryptographic hashes and require hash validation: ```text ollama-herd==<reviewed-version> \ --hash=sha256:<verified-distribution-hash> ``` Install it with: ```bash python3 -m pip install --require-hashes -r requirements.txt ``` 3. Verify and update the pinned version through a controlled dependency-review process rather than automatically selecting the latest release. 4. Recommend installation in a dedicated virtual environment under a non-privileged account: ```bash python3 -m venv .venv . .venv/bin/activate python3 -m pip install --require-hashes -r requirements.txt ``` 5. Explicitly warn users not to run pip or the package commands with administrator or root privileges. 6. Where practical, document the expected package publisher, source repository, release provenance, and artifact digest so users can independently validate the dependency. ]]>