T03 · Remote Payload Retrieval and Execution
Error
- Location
SKILL.md:21- Finding
Unverified Remote Installer Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–28
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
bash If `MEMKEEPER_BIN` is absent, download the public installer to a temporary file, inspect it, and run it. Do not paste secrets into a command or config file. ```bash curl -fsSL https://raw.githubusercontent.com/teflon07/memkeeper/main/install.sh \ -o /tmp/memkeeper-install.sh bash /tmp/memkeeper-install.shtext ### Technical Analysis The Skill instructs the agent to download a shell script from a personal GitHub repository's mutable `main` branch and execute it with `bash`. It does not pin the download to an immutable commit or release, nor does it verify a checksum or cryptographic signature. Although the prose says to inspect the installer, the provided command sequence contains no inspection, integrity check, or explicit approval gate. Consequently, the payload that executes can differ from the content reviewed during the Skill audit. Using the predictable `/tmp/memkeeper-install.sh` path also provides weaker temporary-file handling than a securely created, owner-restricted temporary directory. Installing Memkeeper is relevant to the declared functionality, but granting a mutable remote script arbitrary command execution exceeds the minimum authority required. The later commands trust the resulting executable to download models, operate on the user's memory store, and act as an OpenClaw MCP server. ### Attack Path 1. An attacker compromises or otherwise gains control of the upstream GitHub account, repository, or mutable `main` branch. 2. The attacker modifies `install.sh` to include malicious shell commands while preserving expected installation behavior. 3. A user or agent follows the Skill when `MEMKEEPER_BIN` is absent. 4. `curl` downloads the altered installer without validating a pinned digest or signature. 5. `bash /t ...[truncated 1178 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
main-branch URL with an official, immutable, versioned release artifact or commit-pinned source. - Publish and verify a SHA-256 or stronger digest before executing or installing anything. Prefer cryptographic signature verification using a separately distributed, trusted public key.
- Avoid executing remote shell installers where a signed package or directly verifiable binary is available.
- If an installer is unavoidable, vendor a reviewed copy in the Skill package or pin its exact content, inspect it before use, and require explicit operator approval before execution.
- Fail closed if the version, checksum, signature, origin, or expected file type cannot be verified.
- Create temporary files with
mktempinside an owner-restricted directory, apply restrictive permissions, and remove them after installation. - Run installation with the least-privileged user and reject unexpected requests for
sudo, system-level service installation, or access outside documented directories. - Verify the installed binary's digest before registering it as an MCP server, and constrain its executable and filesystem permissions where practical.
- Pin and validate model artifacts downloaded by
pull-modelswhen the upstream supports integrity metadata.
- Replace the mutable
