T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:66
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, line 66 **Vulnerability Type**: Unpinned dependency installation **Risk Level**: Medium ```bash pipx install agent-bom ``` ### Technical Analysis The documented installation command retrieves `agent-bom` without specifying a version, package hash, lockfile, or verified provenance. Consequently, the package installed at execution time may differ from the version reviewed when this skill was published. Although the referenced package name and PyPI source do not exhibit an evident typosquatting pattern, the project contains only `SKILL.md`; it does not include the dependency's source code or other artifacts that would allow its implementation to be audited locally. The claims concerning local-only processing, credential handling, telemetry, and network behavior therefore cannot be verified from this repository. ### Attack Path 1. An attacker compromises the upstream PyPI project, a maintainer account, the release pipeline, or a future package release. 2. The attacker publishes a modified version under the legitimate `agent-bom` package name. 3. A user follows the documented `pipx install agent-bom` command. 4. Because no version or integrity constraint is present, `pipx` resolves the attacker-controlled or otherwise unsafe release. 5. Malicious package installation logic or subsequently invoked CLI functionality executes in the installing user's context. ### Impact Assessment A compromised dependency could execute code with the privileges of the user running `pipx`. Depending on that user's permissions, this may expose accessible files, environment variables, source repositories, and credentials, or permit modification of user-owned files and programs. The affected scope is normally limited to the installing user's authority unless installation is performed from a privileged account. No privilege-escalation mechanism is present in the audited file itself.
- Remediation
- ## Remediation Suggestions - Pin the dependency to the reviewed release declared by the skill, for example: ```bash pipx install "agent-bom==0.104.0" ``` - Publish and verify cryptographic hashes or signed provenance for the expected distribution artifacts before installation. - Use a controlled package index or an internally mirrored and reviewed artifact for security-sensitive deployments. - Re-audit the package whenever the pinned version is updated. - Where practical, include the relevant source or a reproducible-build reference so the implementation can be compared with the distributed artifact. - Document that optional Snyk enrichment introduces network communication and ensure `SNYK_TOKEN` remains in the operator environment and is not logged or embedded in generated output.