T08 · Insecure Dependencies
- Location
SKILL.md:48- Finding
Unpinned External Plugin Installation and Broad Tool Allowlisting
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 48-50
Vulnerability Type: Supply-chain exposure through an unpinned executable dependency
Risk Level: HighVulnerable Code
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartTechnical Analysis
The installation workflow retrieves an external plugin by a mutable package identifier without specifying an immutable version, checksum, signature, or reviewed source revision. It then adds the entire plugin to the allowed-tool configuration and restarts the gateway, causing the newly installed executable component to become active.
The audited project contains only
SKILL.md; it does not contain the plugin implementation. Consequently, the effective behavior and security properties of the installed component cannot be verified from this artifact. A compromised registry account, malicious package update, or dependency-source compromise could change the plugin behavior after this Skill has been reviewed.Allowlisting the plugin as a whole rather than an explicit set of required ServiceNow operations further increases the exposed privilege surface. The presence of unrelated SendGrid tools elsewhere in the document demonstrates that the plugin may expose capabilities beyond the declared ServiceNow integration scope.
Attack Path
- An attacker compromises the plugin publishing account, distribution channel, or a future mutable release of
clawlink-plugin. - A user or Agent follows the documented installation command.
- OpenClaw retrieves and installs the compromised plugin because no immutable version or integrity value is required.
- The configuration command allowlists the plugin as an available tool provider.
- The gateway restart loads the installed component.
- The compromised component executes within the plugin's granted context ...[truncated 659 chars]
- An attacker compromises the plugin publishing account, distribution channel, or a future mutable release of
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an immutable, reviewed version or content-addressed release rather than a mutable package identifier.
- Verify a cryptographic checksum or trusted publisher signature before installation.
- Publish or vendor the exact plugin source used by the Skill so its effective behavior can be audited.
- Replace whole-plugin allowlisting with a least-privilege allowlist containing only the ServiceNow tools required by this Skill.
- Isolate the plugin in a restricted runtime with minimal filesystem, network, process, and credential access.
- Require explicit administrative approval before installation, configuration modification, and gateway restart.
- Establish dependency monitoring and revoke affected releases promptly if the publisher or distribution channel is compromised.
