T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unpinned Privileged Third-Party Integration Cannot Be Audited
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47–49; related credential-proxy behavior at lines 71–77
Vulnerability Type: Unpinned and unauditable third-party dependency
Risk Level: MediumVulnerable Code Snippet
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartRelated authentication instructions:
markdown **No API key is required in chat.** ClawLink stores credentials securely and injects them into every GIPHY API request on the user's behalf. ### Getting Connected 1. Install the ClawLink plugin (see Install above). 2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet. 3. Open https://claw-link.dev/dashboard?add=giphy and connect GIPHY. 4. Call `clawlink_list_integrations` to verify the connection is active.Technical Analysis
The Skill instructs the user or agent to install
clawlink-pluginwithout pinning an exact version or immutable digest. It then explicitly adds the plugin to OpenClaw's allowed tool set and restarts the gateway.The plugin implementation, dependency manifest, and permission manifest are not included in the audited project. Consequently, this audit cannot verify:
- Which plugin version will be resolved at installation time.
- Whether later installations can resolve to changed code.
- What local permissions the plugin receives.
- Which remote endpoints it can contact.
- How authentication credentials are stored, retained, encrypted, or revoked.
- Whether proxied request bodies or uploaded assets are logged or forwarded elsewhere.
The documented intermediary behavior is relevant to the Skill's GIPHY functionality: authenticated network requests are necessary to access the API, and uploads inherently transmit user-selected media. Nevertheless, routing credentials and requests through an external service expands the trust boundary beyond a direct GIPHY integrati ...[truncated 2198 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a reviewed, exact version and preferably an immutable cryptographic digest.
- Publish or reference reproducible source code corresponding to the pinned artifact.
- Verify package signatures and checksums before installation.
- Provide a permission manifest documenting local resources, available tools, network destinations, and credential access.
- Restrict outbound traffic to explicitly documented ClawLink and GIPHY endpoints.
- Separate read-only discovery permissions from upload permissions. Enable write capability only when the user requests an upload.
- Preserve the existing preview and explicit-confirmation requirements for every upload.
- Document credential encryption, retention, logging, revocation, and incident-response behavior.
- Prefer direct GIPHY authentication where feasible. If an intermediary remains necessary, obtain informed user consent explaining that credentials and requests pass through it.
- Provide removal and revocation instructions covering plugin uninstall, allowlist removal, session invalidation, and GIPHY credential revocation.
- Avoid automatically repeating installation or gateway-modification commands during troubleshooting without first verifying the installed package and configuration state.
