T08 · Insecure Dependencies
- Location
SKILL.md:48- Finding
Unpinned External Plugin Receives Broad Access to Cloud Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 48-84
Vulnerability Type: Unpinned third-party dependency with access to Microsoft OAuth credentials and OneDrive data
Risk Level: MediumVulnerable Code
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartmarkdown All OneDrive tool calls are authenticated automatically by ClawLink using the user's connected Microsoft account. **No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Microsoft Graph 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=onedrive and connect OneDrive. 4. Call `clawlink_list_integrations` to verify the connection is active.Technical Analysis
The skill instructs the agent to install and allowlist
clawlink-pluginwithout specifying an immutable version, package digest, signature, or integrity check. The plugin implementation is not included in the audited project, so its executable behavior, update process, token handling, and enforcement of request boundaries cannot be verified from the available source.After installation, the gateway is restarted and the plugin is authorized as an available tool provider. The documentation also states that ClawLink stores the user's OAuth token and injects it into Microsoft Graph requests. Consequently, the external plugin and hosted service occupy a security-sensitive position with access to authenticated OneDrive and SharePoint operations.
This is a supply-chain risk rather than evidence that the current plugin is malicious. However, installing an unpinned component permits its effective implementation to change after this skill has been r ...[truncated 1469 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
clawlink-pluginto a reviewed, immutable version and preferably a cryptographic package digest. - Verify a publisher signature and checksum before installation, and fail closed if verification fails.
- Publish or vendor the relevant plugin source so its token handling, network destinations, update behavior, and request authorization can be audited.
- Document the exact Microsoft OAuth scopes requested and remove permissions not required for the intended OneDrive operations.
- Separate read-only and write-capable authorization where Microsoft Graph permits it, using read-only access by default.
- Prefer per-skill or per-session authorization over global plugin allowlisting.
- Require explicit, transaction-bound confirmation for uploads, modifications, deletions, permission changes, and sharing operations.
- Restrict outbound communication to documented ClawLink and Microsoft Graph endpoints.
- Provide users with clear procedures to revoke Microsoft consent, invalidate active tokens, disconnect the integration, and remove the plugin.
- Maintain an auditable update policy with security review, release provenance, and rollback support for every plugin version.
- Pin
