T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:61
- Finding
- Unverified Remote Installer Download and Immediate Shell Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 61–65 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High ### Vulnerable Code ```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 retrieve mutable scripts from `cli.oomol.com` and immediately execute them through `bash` or PowerShell's `Invoke-Expression`. The downloaded content is not pinned to a specific release and is not subject to checksum validation, cryptographic signature verification, or local inspection before execution. Installing the `oo` CLI is relevant to the Skill's declared DataForB2B functionality. However, executing an unverified remote response directly in a shell exceeds the minimum privileges safely necessary to perform that installation. The effective code can change after the Skill has been audited without requiring any modification to the reviewed `SKILL.md` file. Both commands create a remote code-execution channel. A compromise of the download domain, its hosting or deployment pipeline, DNS resolution, or the relevant TLS trust chain could cause arbitrary attacker-controlled code to run on the user's machine. ### Attack Path 1. The `oo` CLI is absent, causing a `command not found` error. 2. The agent or user follows the documented first-time setup instructions. 3. An attacker compromises or gains control over the installer response through the hosting infrastructure, publication pipeline, domain, or applicable network trust path. 4. The attacker returns a modified shell or PowerShell installer. 5. `bash` or `Invoke-Expression` executes the response immediately, without integrity or authenticity verification. 6. The payload performs arbitrary actions using the privileges of the account that invoked the installation command. ### Impact Assessment Successful e ...[truncated 910 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the direct `curl | bash` and `Invoke-RestMethod | Invoke-Expression` installation commands. 2. Pin installation instructions to a specific, reviewed CLI release rather than a mutable installer endpoint. 3. Download the installer or release artifact to a local file without executing it automatically. 4. Verify the artifact using a publisher-provided cryptographic signature or a SHA-256 checksum obtained through an independently authenticated channel. 5. Display or otherwise make the downloaded installer available for inspection before execution. 6. Require explicit user approval before installing software or running any downloaded script. 7. Prefer a trusted package manager or signed platform-native package where available. 8. Run installation with ordinary user privileges unless a specific installation step demonstrably requires elevation. 9. If a remote installer remains necessary, use a versioned immutable URL, fail closed on verification errors, and document the expected publisher identity and checksum.