T03 · Remote Payload Retrieval and Execution
- Location
references/runtime-setup.md:11- Finding
Mutable Remote Repository Is Cloned and Its Scripts Are Executed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
references/runtime-setup.md:11-14
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
bash git clone https://github.com/dmoraine/clawEASA.git cd clawEASA ./scripts/bootstrap-local-runtime.sh ./scripts/install-openclaw-skill.shTechnical Analysis
The documented installation procedure clones the current default branch of a remote GitHub repository and immediately executes two scripts from that checkout. It does not pin an immutable commit or release, verify a cryptographic checksum or signature, or provide the scripts within the audited artifact.
Consequently, the effective code executed by users can change after this skill package has been reviewed. The referenced bootstrap scripts, dependency declarations, and lockfiles are absent from the audited project, so their behavior and transitive dependencies cannot be verified from this artifact.
This creates a remote code-execution supply-chain boundary: anyone able to alter the upstream repository or its distribution path could change either script and have the modified payload executed by users following the documented setup.
Attack Path
- An attacker compromises the upstream repository, a maintainer account, or another mechanism capable of modifying its default branch.
- The attacker inserts malicious commands into
scripts/bootstrap-local-runtime.sh,scripts/install-openclaw-skill.sh, or content invoked by those scripts. - A user follows the installation instructions and clones the mutable default branch.
- The user executes both downloaded scripts without performing an integrity or source review.
- The malicious commands run with the privileges and environment access of the installing user.
Impact Assessment
Successful exploitation permits arbitrary command execution with the installing user's privileges. Depending on that user's permiss ...[truncated 431 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the clone to a reviewed, immutable commit hash rather than relying on the repository's mutable default branch.
- Publish signed releases and verify the release signature or a trusted cryptographic checksum before executing any downloaded content.
- Include the required installation scripts, dependency manifests, and lockfiles in the auditable skill distribution where feasible.
- Display or review downloaded scripts before execution, and avoid combining remote retrieval with immediate script execution.
- Pin all Python and system dependencies to reviewed versions with hashes, then verify them during installation.
- Run bootstrap operations with the least-privileged account possible and avoid requesting administrator or root access.
- Add automated integrity checks that fail closed if the checked-out revision or script hashes differ from approved values.
