T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:147
- Finding
- Unpinned Remote Skill Repository Installed into an Auto-Discovered Directory## Vulnerability Details **File Location**: `SKILL.md`, lines 147-159 **Vulnerability Type**: Unverified and mutable third-party Skill dependency **Risk Level**: Medium ### Vulnerable Code ```bash # Clone the complete repository into the skills directory git clone https://github.com/kepano/obsidian-skills.git ~/.openclaw/workspace/skills/obsidian-skills ``` ```text The complete repository must be cloned. The expected directory structure is: ~/.openclaw/workspace/skills/obsidian-skills/skills/<skill-name>/SKILL.md OpenClaw automatically discovers all SKILL.md files under ~/.openclaw/workspace/skills/. ``` ### Technical Analysis The documented installation procedure clones the current default branch of a remote repository without pinning a reviewed commit or signed release and without verifying a checksum or cryptographic signature. It places the entire repository directly inside OpenClaw's Skill discovery directory. Consequently, the effective installed content is mutable and is not limited to the project file reviewed in this audit. A compromise of the upstream repository or maintainer account, or an unsafe future upstream revision, could introduce attacker-controlled Skill instructions. Because OpenClaw automatically discovers `SKILL.md` files in the destination hierarchy, such instructions may become available to the agent after installation and restart. This is classified as an insecure dependency rather than confirmed malicious payload retrieval: the reviewed command only clones content, and the audited project contains no evidence that fetched code is automatically executed. The risk arises from trusting unpinned remote components in an auto-discovered instruction location. ### Attack Path 1. An attacker compromises the upstream repository, a maintainer account, or the repository's mutable default branch. 2. The attacker adds or modifies one or more `SKILL.md` files with unsafe or instruction-hijacking ...[truncated 1199 chars]
- Remediation
- ## Remediation Suggestions 1. Pin installation to a specific, previously reviewed commit hash or cryptographically signed release rather than cloning a mutable default branch. 2. Publish and verify a trusted checksum or signature for the exact archive or commit being installed. 3. Download or clone the repository into a staging directory outside `~/.openclaw/workspace/skills/`. 4. Review the complete pinned revision before installation, including every discovered `SKILL.md`, script, symlink, and configuration file. 5. Copy only explicitly approved Skill directories into OpenClaw's discovery path instead of installing the complete repository. 6. Disable or restrict automatic Skill discovery where possible and require explicit allowlisting. 7. Run OpenClaw with least privilege and limit the filesystem, credential, network, and tool access available to third-party Skills. 8. Document a controlled update process that repeats signature verification and security review before changing the pinned revision.
