T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installer Download and Execution<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **Vulnerability Type**: Remote payload retrieval and execution through pipe-to-shell installation commands **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 download mutable scripts from `cli.oomol.com` and immediately execute them using `bash` or PowerShell's `Invoke-Expression`. Neither command pins a release version, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded content before execution. Although the download domain appears related to the declared OOMOL service, the effective code executed by these commands is controlled remotely and can change after the Skill has been reviewed. Compromise of the hosting service, release pipeline, DNS/TLS infrastructure, or installer content could consequently result in arbitrary code execution. Installing a CLI may be necessary when the required command is unavailable, but unverified pipe-to-shell execution exceeds the minimum privileges needed for the Skill's declared read-only Pilvio operations. The issue is partially constrained because the instructions say to use installation only after an `oo: command not found` error. ### Attack Path 1. The Skill attempts to perform a Pilvio operation using the `oo` CLI. 2. The command fails because `oo` is not installed. 3. The agent or user follows the documented first-time setup instructions. 4. The system retrieves the current installer from `https://cli.oomol.com/install.sh` or `https://cli.oomol.com/install.ps1`. 5. The downloaded response is passed directly to `bash` or `Invoke-Expression` without integrity verification. 6. If the remote installer or its delivery infrastructure has been compromised, attacker-contr ...[truncated 738 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Remove both direct pipe-to-shell installation patterns. 2. Prefer an official package manager or a version-pinned release artifact from the publisher's official repository. 3. Download the installer as a separate file rather than executing the network response directly. 4. Publish an expected SHA-256 or stronger cryptographic digest through an independently trusted channel and verify it before execution. 5. Where supported, verify a publisher signature and validate the signing identity. 6. Display or otherwise permit inspection of the installer before execution. 7. Require explicit user approval before installing software, even when the `oo` command is missing. 8. Run the installer with ordinary user privileges and avoid elevation unless a clearly documented installation step strictly requires it. 9. Pin the documented installer or CLI version so that the reviewed artifact corresponds to the artifact users receive. 10. Preserve the existing behavior of attempting normal connector operations first, and present safe manual installation instructions only after a confirmed missing-command error. ]]>
