T08 · Insecure Dependencies
- Location
SKILL.md:52- Finding
Unpinned Third-Party Plugin Receives Privileged Snowflake Access
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 52–54 and 73–76
Vulnerability Type: Unpinned and externally managed dependency with access to sensitive credentials and database operations
Risk Level: HighVulnerable Code
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartThe plugin is subsequently trusted to handle Snowflake authentication:
text All Snowflake tool calls are authenticated automatically by ClawLink using the user's connected Snowflake account credentials. No credentials are required in chat. ClawLink stores the connection credentials securely and injects them into every Snowflake API request on the user's behalf.Technical Analysis
The Skill instructs the user or agent to install
clawhub:clawlink-pluginwithout specifying an immutable version, cryptographic digest, or verified source revision. It then explicitly allowlists the plugin and restarts the OpenClaw gateway, activating third-party code whose implementation is not included in the audited project.The same dependency is trusted to store or mediate Snowflake credentials and proxy authenticated requests. Its exposed capabilities include raw SQL execution, DDL and DML operations, warehouse administration, user and role enumeration, and file uploads to internal stages. Because the plugin source and version are absent, the audit cannot verify its credential handling, confirmation enforcement, request validation, update behavior, or resistance to supply-chain compromise.
A mutable dependency identifier means that code installed at a later time may differ from the code originally reviewed or expected. If the registry entry, publisher account, release pipeline, or plugin distribution channel is compromised, malicious code could execute with the permissions granted to the plugin and connect ...[truncated 2071 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an immutable, reviewed version rather than installing a mutable package identifier.
- Require cryptographic signature and digest verification before installation and before every update.
- Publish or bundle the plugin source and reproducible build metadata so its credential handling and operation-confirmation controls can be independently audited.
- Use a dedicated Snowflake service identity or role with only the minimum permissions required for the requested workflow.
- Separate read-only and write-capable integrations. Do not grant DDL, DML, warehouse administration, user administration, or stage-write privileges unless explicitly required.
- Enforce write approval outside the third-party plugin so a compromised dependency cannot bypass confirmation requirements.
- Restrict outbound communication to documented ClawLink and Snowflake endpoints and monitor for unexpected network destinations.
- Document credential storage, encryption, retention, rotation, revocation, and incident-response procedures.
- Log and audit all plugin installation events, updates, Snowflake queries, administrative operations, and stage uploads.
- Provide an explicit uninstall and credential-revocation procedure for suspected plugin or supply-chain compromise.
