T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:58
- Finding
- Unverified Remote Installer Scripts Are Executed Directly## Vulnerability Details **File Location**: `SKILL.md`, lines 58–62 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ``` ### Technical Analysis The first-time setup instructions download mutable scripts from `cli.oomol.com` and immediately execute them through Bash or PowerShell. Neither command pins an audited release nor verifies a cryptographic checksum or publisher signature before execution. HTTPS protects the connection in transit but does not establish that the retrieved script is the same code that was reviewed. The effective payload may change at any time. Compromise of the hosting service, publishing account, DNS/PKI path, or installer infrastructure could therefore turn these documented commands into an arbitrary code-execution channel. Installing the required CLI is related to the Skill's functionality, but piping an unverified response directly into a shell exceeds the minimum privilege and trust necessary to perform that installation. The artifact can instead be downloaded, inspected, authenticated, and installed with explicit approval. ### Attack Path 1. The `oo` command is unavailable, causing the agent or user to consult the first-time setup instructions. 2. An attacker compromises or gains control over the remote installer response or its delivery infrastructure. 3. The agent or user executes the documented `curl | bash` or `irm | iex` command. 4. The shell executes the attacker-controlled response immediately, without integrity or authenticity verification. 5. The payload performs arbitrary operations under the permissions of the account that launched the command. ### Impact Assessment Successful exploitation provides arbitrary command execution with the invoking user's privileges. Dependin ...[truncated 546 chars]
- Remediation
- ## Remediation Suggestions 1. Remove direct `curl | bash` and `irm | iex` execution from the setup instructions. 2. Pin installation instructions to a specific, audited CLI version rather than a mutable generic installer URL. 3. Download the installation artifact to a local file before executing it. 4. Publish a cryptographic checksum through a separately protected release channel and verify it locally before installation. 5. Prefer signed packages or binaries and validate the publisher signature against a documented trusted key. 6. Display the verified installation command and request explicit user approval before execution. 7. Use the operating system's trusted package manager where an official, version-pinned package is available. 8. Run installation with ordinary user privileges unless a specific installation step demonstrably requires elevation; isolate any elevated operation and clearly explain its effect. 9. For PowerShell, invoke a downloaded and verified script file directly rather than evaluating a network response with `Invoke-Expression`.