T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned Remote Skill Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 35–40
Vulnerability Type: Unpinned third-party skill installation
Risk Level: MediumVulnerable Code Snippet
markdown Installation rule: - Only after explicit user approval, install the exact audited core skill with the runtime's standard ClawHub install flow: `clawhub install suka233/kmind-markdown-to-mindmap --workdir ./` - Never substitute another slug, including localized variants.Technical Analysis
The installation command identifies the remotely hosted skill only by its mutable ClawHub slug. It does not pin an immutable release version, commit identifier, or cryptographic digest. Consequently, the implementation installed in the future may differ from the implementation that was originally audited.
The dependency's source code is not included in this repository, so this audit cannot verify its effective behavior. Explicit user approval reduces the likelihood of an unnoticed installation, and restricting installation to an exact slug helps prevent accidental substitution, but neither control verifies the integrity of the payload associated with that slug.
Attack Path
- An attacker compromises the upstream publisher account, distribution infrastructure, or release process for
suka233/kmind-markdown-to-mindmap. - The attacker publishes a modified skill under the same permitted slug.
- The wrapper detects that the core skill is unavailable and requests installation approval.
- The user approves the documented installation.
- The Agent runs
clawhub install suka233/kmind-markdown-to-mindmap --workdir ./without verifying an immutable version or digest. - The wrapper delegates the user-provided note or Markdown content to the modified dependency.
- The modified dependency executes within the permissions and environment available to the Agent runtime.
Impact Assessment
A compromised upstream dependency c ...[truncated 603 chars]
- An attacker compromises the upstream publisher account, distribution infrastructure, or release process for
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an immutable, audited version rather than installing only by slug.
- Record and verify a cryptographic digest or trusted signature before installation.
- Document the exact upstream release, source revision, and digest that were reviewed.
- Reject installation if the retrieved artifact does not match the approved identity and integrity metadata.
- Require renewed user approval whenever the pinned version or expected digest changes.
- Run the installed renderer with least privilege, restricting filesystem access to the explicitly supplied input and designated output location.
- Disable unnecessary network access while processing note content where supported by the runtime.
- Periodically re-audit the exact pinned upstream release and its transitive dependencies.
