T08 · Insecure Dependencies
- Location
SKILL.md:53- Finding
Unpinned Third-Party Plugin Installation and Activation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 53–57
Vulnerability Type: Unpinned privileged third-party dependency
Risk Level: Mediumbash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartTechnical Analysis
The installation command references
clawhub:clawlink-pluginwithout specifying an immutable version, package digest, checksum, or signature verification step. The following command explicitly allowlists the installed plugin, and the gateway restart activates it.Consequently, the code reviewed during an audit may differ from the code installed later. Although the document describes the plugin as “verified,” that statement does not provide enforceable artifact integrity. If the package registry, publisher account, distribution infrastructure, or latest plugin release is compromised, users following these instructions could install and activate attacker-controlled code.
The plugin is intended to mediate ClickUp operations and managed authentication, so compromise could expose integration data and permit operations within the connected account’s effective authorization scope.
Attack Path
- An attacker compromises the plugin publisher account, package registry, release pipeline, or another upstream distribution component.
- The attacker publishes or substitutes a malicious release under the same mutable
clawhub:clawlink-pluginidentifier. - A user or agent follows the documented installation command, which retrieves the current upstream release without pinning or integrity verification.
- The plugin is added to
tools.alsoAllow, granting it access through the OpenClaw tool configuration. - The gateway is restarted, activating the compromised plugin.
- The malicious plugin can process subsequent integration calls and potentially access or manipulate data available through the plugin and connected ClickUp account ...[truncated 563 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an audited, immutable version and, where supported, a cryptographic artifact digest.
- Add an explicit signature or checksum verification step before installation and fail closed if verification is unsuccessful.
- Obtain the plugin only from an authenticated, trusted registry whose namespace ownership and release provenance can be verified.
- Document the precise permissions, data access, and host capabilities granted to the plugin before requesting user approval.
- Require separate explicit approval for installation, allowlisting, and gateway restart rather than treating them as one automatic setup sequence.
- Apply least privilege to the plugin and connected ClickUp account, restricting workspace permissions to capabilities required for the requested task.
- Review and test each new plugin release before updating the pinned version.
- Maintain a rollback procedure and audit logs for plugin installation, configuration changes, authentication activity, and ClickUp operations.
