T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:62
- Finding
- Unverified Remote Installer Execution## Vulnerability Details **File Location**: `SKILL.md:62` **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High ### Vulnerable Code ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ### Technical Analysis The installation instruction downloads a mutable shell script from an external URL and immediately pipes it into Bash. It does not pin the installer to a reviewed version, verify a cryptographic signature or checksum, or provide an opportunity to inspect the downloaded content before execution. Consequently, the effective code executed by this Skill can change after the Skill package has been audited. Although the URL uses HTTPS and its domain is associated with the documented CLI, HTTPS alone does not protect against compromise of the publisher, hosting infrastructure, release process, domain, or trusted TLS environment. Installing the CLI is only a fallback when `oo` is unavailable, not part of ordinary Simplesat connector operations. Automatically executing mutable remote code therefore exceeds the minimum privileges needed for normal Skill functionality. ### Attack Path 1. The `oo` command is unavailable, causing the first-time setup instructions to be used. 2. An attacker compromises the installer publication process, hosting infrastructure, domain resolution, or another trusted delivery component. 3. The attacker replaces or alters `install.sh` with malicious shell commands. 4. `curl` retrieves the current attacker-controlled response. 5. The pipe sends that response directly to Bash without integrity verification or review. 6. The payload executes with the privileges and environment of the user running the command. ### Impact Assessment Successful exploitation provides arbitrary code execution with the invoking user's privileges. The payload could read or modify files accessible to that user, access environment variables and local credentials, ...[truncated 291 chars]
- Remediation
- ## Remediation Suggestions - Do not pipe downloaded content directly into a shell. - Pin installation to a specific, reviewed CLI release. - Download the installer or binary to a local file before execution. - Verify a publisher signature and a SHA-256 checksum obtained through an independently protected channel. - Display the source, destination, permissions, and expected system changes before requesting explicit user approval. - Prefer a trusted operating-system package manager or signed release artifact with version pinning. - Run installation with ordinary user privileges unless a documented component strictly requires elevation.
