T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:58
- Finding
- Unverified Remote Shell Script Execution## Vulnerability Details **File Location**: `SKILL.md`, line 58 **Vulnerability Type**: Remote payload retrieval and immediate shell execution **Risk Level**: High **Vulnerable Code**: ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ### Technical Analysis The installation instruction pipes a remotely retrieved, mutable script directly into Bash. The script is not pinned to a specific version, downloaded for inspection, or verified using a cryptographic signature or trusted checksum. Although HTTPS protects the connection in transit under normal conditions, it does not protect against compromise of the publisher, hosting infrastructure, DNS resolution, certificate issuance, or the installation endpoint itself. It also does not prevent the publisher-controlled script from changing after the Skill has been reviewed. Installing the CLI may be necessary when it is missing, but immediate execution of unverified remote content is not necessary for the Skill's declared read-only Documenso functionality and exceeds least-privilege expectations. ### Attack Path 1. The `oo` CLI is unavailable, causing the first-time setup instructions to be used. 2. An attacker compromises or gains control over `https://cli.oomol.com/install.sh` or its delivery infrastructure. 3. The attacker replaces or modifies the response with malicious shell commands. 4. `curl` retrieves the attacker-controlled response. 5. The pipe passes the response directly to Bash without verification or review. 6. Bash executes the payload with the privileges of the user running the setup command. ### Impact Assessment Successful exploitation provides arbitrary command execution under the invoking user's account. The payload could read or modify accessible files, steal credentials and session material, alter the CLI, install malware, or establish persistence. If the installation command is run from an elevated shell, the payload ...[truncated 108 chars]
- Remediation
- ## Remediation Suggestions Remove the pipe-to-shell installation instruction. Prefer a trusted operating-system package manager with a pinned CLI version. If direct installation is unavoidable: 1. Download a versioned artifact to a local file without executing it. 2. Obtain the expected checksum or signature through a separately authenticated release channel. 3. Verify the artifact using a cryptographically secure digest or publisher signature. 4. Allow the user to inspect the script and explicitly approve execution. 5. Execute it without elevated privileges unless a documented installation step strictly requires elevation. 6. Pin the documented installer or release version so the effective payload cannot silently change after review.
