T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned CLI Installation from a Third-Party Homebrew Tap
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumComplete Code Snippet:
yaml metadata: {"clawdbot":{"emoji":"💎","requires":{"bins":["obsidian-cli"]},"install":[{"id":"brew","kind":"brew","formula":"yakitrak/yakitrak/obsidian-cli","bins":["obsidian-cli"],"label":"Install obsidian-cli (brew)"}]}}Technical Analysis
The Skill declares
obsidian-clias a required executable and provides an installation instruction that retrieves it from the third-party Homebrew tapyakitrak/yakitrak. The dependency is not constrained to a specific version, formula revision, commit, checksum, or cryptographic signature.Consequently, the code installed for the same formula identifier can change after this Skill has been reviewed. The listed homepage,
https://help.obsidian.md, does not establish that this third-party CLI or Homebrew tap is an official Obsidian distribution. If the tap, its maintainer account, its upstream release process, or a referenced artifact is compromised, attacker-controlled code could be delivered through the dependency installation process.Attack Path
- A user or Skill-management framework determines that the required
obsidian-cliexecutable is unavailable. - The declared Homebrew installation procedure resolves
yakitrak/yakitrak/obsidian-cli. - An attacker compromises the third-party tap, a maintainer account, the upstream release source, or an artifact referenced by the formula.
- Because the dependency is mutable and no version or integrity value is pinned by the Skill, Homebrew retrieves the compromised formula or artifact.
- Malicious installation logic or a malicious CLI binary executes with the privileges of the user running Homebrew.
- The compromised CLI can abuse its expected access to Obsidian vaults and local files when subsequently invoked.
Impact Assessment
Successful exp ...[truncated 654 chars]
- A user or Skill-management framework determines that the required
- Remediation
View remediation
Remediation Suggestions
- Prefer an official, authenticated distribution of the CLI if one is available.
- If the third-party tap must be retained, pin the dependency to an audited release and immutable formula revision or commit.
- Verify downloaded artifacts with a trusted cryptographic checksum or signature before installation.
- Record the expected version and integrity value in the Skill metadata or in a controlled installation script that fails closed on verification errors.
- Review the Homebrew formula and all transitive download sources before approving updates.
- Clearly disclose that
obsidian-cliis a third-party component and require explicit user confirmation before installing it. - Run installation and CLI operations with the minimum necessary user permissions, without administrative elevation, and limit access to the intended vault where feasible.
- Use automated dependency monitoring so changes to the formula, tap ownership, release artifacts, or checksums trigger a new security review.
