T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Executable Dependency Uses a Mutable Latest Version
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10–17
Vulnerability Type: Supply-chain risk from an unpinned executable dependency
Risk Level: MediumComplete Code Snippet:
yaml "install": [ { "id": "go", "kind": "go", "module": "github.com/steipete/blucli/cmd/blu@latest", "bins": ["blu"], "label": "Install blucli (go)", }, ],Technical Analysis
The installation configuration retrieves and compiles
github.com/steipete/blucli/cmd/blu@latest. Thelatestselector is mutable, so the code installed in the future may differ from the code reviewed when this Skill was audited.The project does not provide a fixed release version, immutable commit identifier, vendored dependency, checksum, or other integrity control for this executable dependency. Consequently, the effective behavior of the installed
blubinary depends on the upstream repository and dependency state at installation time.This does not establish that the current upstream package is malicious. It creates a supply-chain exposure in which an upstream repository compromise, maintainer account compromise, malicious future release, or compromised transitive dependency could introduce code that was not part of this audit.
Attack Path
- An attacker compromises the upstream repository, release process, maintainer credentials, or a dependency used by the upstream Go module.
- The attacker publishes malicious code in the version resolved by
@latest. - A user installs or reinstalls the Skill after that publication.
- The Go installation process retrieves and compiles the changed upstream source.
- The resulting executable is installed as
blu. - When the Skill or user invokes
blu, the injected code executes with the privileges and environment of that process.
Impact Assessment
Successful exploitation could execute arbitrary code under the account p ...[truncated 501 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith a specific, reviewed semantic version or immutable commit identifier. - Prefer a release whose provenance and maintainer signatures can be verified.
- Record and verify an expected checksum for distributed binaries or otherwise use an installation mechanism that enforces artifact integrity.
- Review and lock transitive Go module dependencies as part of the release process.
- Automate dependency updates through a controlled workflow that performs source review, vulnerability scanning, tests, and checksum updates before changing the pinned version.
- Install and execute the binary with the least-privileged account required for local BluOS control.
- Replace
