T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:9
- Finding
- Unpinned Third-Party Executable Installed from Mutable Sources<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 9–24 **Vulnerability Type**: Unpinned and insufficiently verified third-party dependency **Risk Level**: Medium ```yaml "requires": { "bins": ["llmfit"] }, "install": [ { "id": "brew", "kind": "brew", "formula": "AlexsJones/llmfit", "bins": ["llmfit"], "label": "Install llmfit (brew tap AlexsJones/llmfit && brew install llmfit)", }, { "id": "cargo", "kind": "node", "bins": ["llmfit"], "label": "Install llmfit (cargo install llmfit)", }, ], ``` ### Technical Analysis The Skill depends on the external `llmfit` executable and offers installation through a third-party Homebrew tap or Cargo. Neither installation method pins an audited version, immutable commit, cryptographic checksum, or artifact digest. Consequently, the dependency retrieved during installation can differ from the version that was previously reviewed. The Homebrew option references the mutable third-party source `AlexsJones/llmfit`. The Cargo command similarly installs the latest available release by default. Compromise of the referenced tap, package registry account, release process, or upstream repository could therefore cause users to install attacker-controlled code. The Cargo installation entry also declares `"kind": "node"` even though its label invokes `cargo install`. This installer-type mismatch introduces ambiguity about how the package manager integration will process the entry and may undermine expected dependency validation. No malicious implementation is embedded in the audited project itself. The risk arises from trusting and executing a mutable external dependency without integrity or version controls. ### Attack Path 1. An attacker compromises the third-party Homebrew tap, Cargo package account, upstream repository, or release pipeline used to distribute `llmfit`. 2. The attacker publishes a modified release under the expected pac ...[truncated 1458 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin `llmfit` to a specific, reviewed version for every supported installation method. 2. Prefer an official and independently verifiable distribution source over a personal or otherwise mutable third-party tap. 3. Pin Homebrew dependencies to an immutable formula revision or commit where the integration supports it. 4. Use an explicit Cargo version, such as `cargo install llmfit --version <reviewed-version> --locked`. 5. Verify downloaded artifacts using a trusted cryptographic checksum, signature, or immutable digest before execution. 6. Record the expected upstream repository and publisher identity so similarly named or substituted packages can be rejected. 7. Correct the Cargo installer metadata from `"kind": "node"` to the appropriate supported Cargo/Rust installer type. 8. Review dependency updates before changing the pinned version, including release artifacts, ownership changes, and transitive dependencies. 9. Run the executable with ordinary user privileges and avoid administrative execution unless it is strictly required and explicitly justified. ]]>