T08 · Insecure Dependencies
- Location
README.md:7- Finding
Unpinned Retrieval of Executable Scripts from a Mutable Repository
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 7-9
Vulnerability Type: Supply-chain risk from an unpinned executable dependency
Risk Level: MediumVulnerable Code:
bash git clone https://github.com/jeffaf/harrypotter-skill.git cd harrypotter-skill chmod +x harrypotter scripts/harrypotterTechnical Analysis
The documented installation procedure clones the current contents of a mutable GitHub repository and marks two downloaded scripts as executable. It does not pin the repository to a reviewed commit, release tag with verified provenance, or immutable artifact checksum.
The audited artifact contains only
README.mdandSKILL.md; it does not contain the referencedharrypotterorscripts/harrypotterfiles. Consequently, the executable behavior users are instructed to install and invoke cannot be verified from the reviewed package. If the upstream repository, its maintainer account, or its default branch were compromised or maliciously modified, subsequent installations could retrieve substituted scripts.This is a supply-chain weakness rather than evidence that the current upstream repository is malicious.
Attack Path
- An attacker compromises the upstream repository, a maintainer account, or another mechanism capable of modifying its default branch.
- The attacker replaces either
harrypotterorscripts/harrypotterwith malicious code. - A user follows the documented installation instructions and clones the mutable repository without commit pinning or integrity verification.
- The user marks the downloaded scripts as executable with
chmod +x. - The agent invokes those scripts according to the usage instructions in
SKILL.md. - The substituted code executes with the operating-system privileges and environment access of the user running the agent.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the invoking use ...[truncated 492 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the referenced executable scripts in the skill artifact so their exact contents are available for review.
- Pin installations to a specific reviewed commit hash instead of implicitly using the repository's mutable default branch.
- Publish versioned, immutable release artifacts and provide SHA-256 or stronger cryptographic checksums.
- Verify artifact signatures or attestations before granting execute permission or running the scripts.
- Document the expected checksum and fail installation if verification does not succeed.
- Run the skill with least privilege in a restricted environment, exposing only the files, environment variables, and network destinations required for its stated API lookup function.
- Add the complete executable source to future audit submissions so network requests, argument handling, shell quoting, and
jqusage can be assessed directly.
