T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:101- Finding
Unverified Remote Installation Script Is Executed Directly by Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:101andMIGRATION-GUIDE.md:113
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: CriticalVulnerable Code
bash curl -fsSL https://openclaw.ai/install.sh | bashTechnical Analysis
The installation instructions pipe a response retrieved from an external URL directly into Bash. The effective executable payload is therefore determined at execution time rather than audit time.
The instructions do not pin a release, verify a cryptographic signature, validate a checksum, or provide an inspection step. HTTPS protects the connection under normal conditions but does not protect users if the server, hosting account, deployment pipeline, DNS/TLS trust path, or installation script is compromised.
This behavior is not required for the migration functionality itself. OpenClaw installation is a prerequisite operation and can be performed through a separately downloaded, authenticated release artifact.
Attack Path
- An attacker compromises the remote installation endpoint, its deployment pipeline, or another component capable of controlling its response.
- A user or agent follows the documented migration instructions.
curlretrieves the attacker-controlled response.- The shell begins interpreting the response immediately, without allowing the user to inspect or authenticate it.
- The payload executes commands with all privileges available to the invoking account.
- If the user invokes the command from an elevated shell, the payload may obtain system-wide privileges.
Impact Assessment
Successful exploitation permits arbitrary command execution with the invoking user's privileges. This can expose OpenClaw data, API credentials, SSH material, private files, agent configuration, and other resources accessible to the account. An elevated invocation could enable system-wide modification or persistence.
- Remediation
View remediation
Remediation Suggestions
- Replace the pipeline with separate download and execution steps.
- Reference an immutable, versioned release artifact rather than a mutable installation URL.
- Publish a SHA-256 digest and a signature from a documented release-signing key.
- Require users to verify both the signature and digest before execution.
- Allow users to inspect the downloaded script locally.
- Do not recommend elevated execution unless a specific operation demonstrably requires it.
- Provide package-manager installation instructions with locked versions where possible.
Example hardened workflow:
bash curl -fSLo install-openclaw.sh \ https://example.invalid/releases/v3.1.0/install-openclaw.sh echo "EXPECTED_SHA256 install-openclaw.sh" | sha256sum -c - less install-openclaw.sh bash install-openclaw.sh
