T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Package and Repository Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16–18 and 124–132
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumThe Skill directs users to install and execute externally maintained code without pinning an exact package version, immutable Git commit, artifact checksum, or cryptographic signature.
Affected code at lines 16–18:
yaml install: - kind: uv package: agent-service-busAffected code at lines 124–132:
bash # Clone the repository git clone https://github.com/qiyueqiu/Agent-Service-Bus.git cd Agent-Service-Bus # Install with uv uv syncTechnical Analysis
The metadata installation retrieves
agent-service-buswithout an exact version constraint. The documented alternative clones the mutable default branch of the external Git repository and then usesuv syncto resolve and install its dependencies.Neither path establishes an immutable relationship between the reviewed Skill and the code ultimately executed. The project contains only
SKILL.md; therefore, the implementation of the installed ASB CLI and MCP server, as well as its transitive dependencies, cannot be verified within the audited artifact.Because package releases, repository branches, and dependency-resolution results can change after review, a future compromised or malicious revision could be installed under the same instructions. This is a supply-chain weakness rather than evidence that the currently referenced project is malicious.
Attack Path
- An attacker compromises the package registry entry, upstream repository, maintainer account, release process, or an unpinned transitive dependency.
- The attacker publishes a malicious package release or modifies the repository's mutable default branch.
- A user installs the Skill dependency through the unversioned
agent-service-busdeclaration, or follows the documentedgit cloneanduv syncprocedu ...[truncated 1054 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
agent-service-busto an exact, reviewed package version rather than allowing the latest available release. - For Git-based installation, check out a full immutable commit hash instead of relying on the repository's mutable default branch.
- Publish and verify cryptographic checksums or trusted signatures for downloaded artifacts.
- Commit and enforce a dependency lockfile that records exact transitive dependency versions and integrity information.
- Ensure the metadata installation and manual installation instructions resolve to the same audited release.
- Review the ASB implementation and its complete dependency tree before exposing it as an MCP server.
- Run the MCP server with least privilege, restricted filesystem access, a sanitized environment, and limited network access.
- Add automated dependency provenance, vulnerability, and integrity checks to the release process.
- Pin
