T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:55
- Finding
- Unreviewed Third-Party Plugin Installation and Update## Vulnerability Details **File Location**: `SKILL.md`, lines 55-64 **Vulnerability Type**: Third-party software supply-chain exposure **Risk Level**: Medium The skill directs the user or agent to install or update executable third-party plugin code that is not included in this project and therefore could not be reviewed as part of this audit. ```bash openclaw plugins install @aramisfa/openclaw-a2a-outbound --pin ``` For an update: ```bash openclaw plugins update openclaw-a2a-outbound ``` Then ensure the plugin entry itself is enabled: ```bash openclaw plugins enable openclaw-a2a-outbound ``` ### Technical Analysis These commands retrieve, install, update, and enable the external `@aramisfa/openclaw-a2a-outbound` package. The external package's source and artifacts are absent from the audited project, so their integrity and runtime behavior cannot be established from `SKILL.md`. The `--pin` option may improve version reproducibility, but the instructions do not require an audited exact version, cryptographic integrity verification, trusted artifact provenance, or review of the resolved package and transitive dependencies. The update command may also retrieve a release published after this skill was reviewed. This creates a supply-chain trust boundary: compromise of the package, publisher account, registry, distribution infrastructure, or a transitive dependency could result in attacker-controlled code being installed and enabled on the OpenClaw Gateway. ### Attack Path 1. An attacker compromises the package publisher, package registry, release pipeline, or an included dependency. 2. The attacker publishes a malicious version or replaces an expected artifact. 3. A user approves the installation or update as required by the skill's interaction rules. 4. The agent or user runs the documented `openclaw plugins install` or `openclaw plugins update` command. 5. OpenClaw retrieves the compromised artifact. ...[truncated 927 chars]
- Remediation
- ## Remediation Suggestions 1. Pin installation to an exact, reviewed package version rather than relying only on a general `--pin` workflow. 2. Verify package integrity using a trusted cryptographic digest or signed provenance before installation. 3. Retrieve packages exclusively from an explicitly configured and trusted registry. 4. Audit the plugin source, release artifact, installation hooks, and transitive dependencies before deployment. 5. Require manual security review and approval before every update; do not update automatically to an unreviewed release. 6. Record the approved version and integrity digest in the skill instructions so operators can verify the resolved artifact. 7. Run the OpenClaw Gateway under a dedicated least-privileged account and restrict filesystem, network, secret, and configuration access to the minimum required. 8. Test new versions in an isolated environment before enabling them on a production Gateway. 9. Provide a documented rollback procedure and retain the last verified artifact and configuration.
