T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–20
Vulnerability Type: Unpinned executable third-party dependency
Risk Level: MediumVulnerable Code Snippet:
markdown ## OpenClaw Plugin Available For full agent tool integration (6 native tools: overleaf_clone, overleaf_branch, overleaf_compile, overleaf_push, overleaf_status, overleaf_health), install the Overleaf plugin: ```bash openclaw plugins install clawhub:@wahajahmed010/openclaw-overleaftext ### Technical Analysis The Skill directs users to install an executable third-party plugin from ClawHub without specifying an immutable version, commit, or integrity checksum. The plugin's source code is not included in the audited project, so the behavior of its six native tools cannot be verified from this artifact. Because the package reference is mutable, code retrieved when the command is executed may differ from the code that existed when the Skill was reviewed. Compromise of the publisher account, package registry, or plugin release process could consequently introduce malicious code into an otherwise trusted workflow. ### Attack Path 1. An attacker compromises the plugin publisher account, the ClawHub package, or its release pipeline. 2. The attacker publishes a malicious update under the referenced package name. 3. A user follows the Skill instructions and executes the unpinned installation command. 4. OpenClaw retrieves and installs the current malicious package version. 5. The plugin executes with the permissions available to the OpenClaw process and its native tools. 6. The malicious plugin can attempt to access local files, credentials, Overleaf projects, Git repositories, or other resources available to that process. ### Impact Assessment Successful exploitation could provide access equivalent to the OpenClaw process executing the plugin. Depending on the host configuration and granted tool permissions, the affec ...[truncated 317 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specific, previously audited immutable version.
- Verify the package with a publisher signature, cryptographic checksum, or equivalent integrity mechanism before installation.
- Include the plugin source and dependency lock data in the security-review scope.
- Document the plugin's required permissions and restrict it to the minimum filesystem, credential, network, and Agent-tool capabilities needed.
- Use an approved internal registry or vetted package allowlist where possible.
- Establish an update-review process rather than automatically trusting later package releases.
