T08 · Insecure Dependencies
- Location
SKILL.md:11- Finding
Unpinned and Mismatched External Skill Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 11-18
Vulnerability Type: Unverified external dependency installation
Risk Level: MediumThe audited artifact identifies itself as
super-agent-knowledge, but its installation instructions direct users to install a separately named and unpinned Skill,knowledge:bash clawhub install knowledgeThis installs
scripts/know— add to PATH or use full path:bash ~/.openclaw/skills/knowledge/scripts/knowTechnical Analysis
The implementation of
scripts/knowis not included in the audited artifact. Consequently, its behavior, permissions, integrity, and security properties cannot be verified from the supplied project files.The dependency is referenced only by the name
knowledge, with no immutable version, integrity digest, repository identity, or trusted registry declaration. This name also differs from the artifact slugsuper-agent-knowledge, as declared in bothSKILL.mdand_meta.json. This creates a supply-chain risk in which installation could resolve to an unintended, replaced, or malicious package. Because no version or digest is pinned, the effective installed code may also change after this artifact has been reviewed.No evidence establishes that the external package is currently malicious. The confirmed weakness is that the artifact asks users to install and execute code outside the audit boundary without sufficient identity or integrity controls.
Attack Path
- A user reviews or loads the
super-agent-knowledgedocumentation. - The user follows the documented command
clawhub install knowledge. - The package manager resolves the separately named and unpinned
knowledgepackage from its configured registry. - An attacker who controls, replaces, or successfully imitates that package supplies a malicious
scripts/knowexecutable. - The user invokes
know, or schedules the documented `know tidy --fix ...[truncated 872 chars]
- A user reviews or loads the
- Remediation
View remediation
Remediation Suggestions
- Include the complete
scripts/knowimplementation within the audited artifact so its behavior is covered by the same review. - Make the installed package name match the declared artifact slug, or explicitly document and justify the relationship between
super-agent-knowledgeandknowledge. - Pin the dependency to an immutable, reviewed version rather than resolving the latest package by name.
- Require an integrity checksum, signed release, or equivalent provenance verification before installation.
- Specify the trusted registry or canonical repository from which the dependency must be obtained.
- Review the executable's filesystem access, command execution, network behavior, and input handling before recommending scheduled execution.
- Avoid adding the tool to cron until the exact executable version and integrity have been verified.
- Include the complete
