T03 · Remote Payload Retrieval and Execution
- Location
README.md:84- Finding
Remote Installer Is Executed Without Integrity Verification
- Content
View full analysis
&2 if curl --retry 3 --retry-all-errors --retry-delay 2 -fsSL "$url" -o "$archive"; then tar -xzf "$archive" -C "$TMP_DIR" find "$TMP_DIR" -mindepth 1 -maxdepth 1 -type d | head -n 1 return 0 fi ``` No cryptographic checksum or signature is verified before the downloaded files are installed and subsequently executed. ### Technical Analysis Piping an HTTP response directly into Bash creates a remote code-execution channel whose effective payload is determined at installation time rather than audit time. TLS protects transport under ordinary conditions, but it does not protect against repository compromise, account compromise, malicious ref replacement, hosting-platform compromise, or an incorrect repository override. The versioned documentation URL reduces exposure to ordinary branch changes, but it does not provide cryptographic integrity verification. The unpinned `main` example is more dangerous because its contents are explicitly mutable. In addition, `CLAUDE_DELEGATE_REPO` and `CLAUDE_DELEGATE_VERSION` can redirect the archive retrieval behavior. ### Attac ...[truncated 1025 chars]- Remediation
View remediation
" "claude-delegate-v0.2.6.tar.gz" | sha256sum -c - tar -xzf claude-delegate-v0.2.6.tar.gz cd openclaw-claude-delegate-0.2.6 less install.sh bash install.sh ``` 4. Verify the downloaded archive inside `install.sh` before extraction. 5. Reject mutable refs such as `main` in production installation paths. 6. Document that installation should be performed as an unprivileged account. 7. If repository overrides remain supported, require an explicit opt-in and a corresponding trusted checksum or signature. ]]>
