T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installer Download and Immediate Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **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 execute them immediately using Bash or PowerShell. Neither command pins a specific installer version, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded content before execution. Although installing the `oo` CLI may be necessary when it is absent, executing an unverified remote response directly in a shell is not the minimum privilege or safest mechanism required to perform that installation. The effective executable payload can change after the Skill has been reviewed. The project contains no evidence that the remote installer is currently compromised; however, its integrity and behavior cannot be established from the audited package. ### Attack Path 1. An attempted OneDesk action fails because the `oo` command is unavailable. 2. The agent or user follows the documented first-time setup instructions. 3. The command retrieves the current response from `https://cli.oomol.com/install.sh` or `https://cli.oomol.com/install.ps1`. 4. Bash or PowerShell executes the response without local verification. 5. If the hosting infrastructure, publishing process, DNS/TLS path, or vendor account has been compromised, attacker-controlled commands execute with the privileges of the invoking user. 6. Those commands can access data available to that user and modify resources permitted by the current operating-system context. ### Impact Assessment Successful exploitation provides arbitrary command execution under the account that runs the installer. T ...[truncated 784 chars]
- Remediation
- ## Remediation Suggestions 1. Remove both pipe-to-shell installation commands. 2. Direct users to a documented, official package manager or versioned release artifact. 3. Pin the CLI to an explicit release version rather than downloading a mutable installer endpoint. 4. Publish cryptographic checksums or signatures through an independently protected channel and verify them before execution. 5. Download the installer to a local file, display its source and expected permissions, and require explicit user approval before running it. 6. Execute installation with ordinary user privileges whenever possible and request elevation only for a specific, documented operation that requires it. 7. Prefer a sequence such as download, signature verification, inspection, and execution rather than combining retrieval and execution in one command. 8. Document the files, directories, network endpoints, and configuration changes the installer will create so users can assess its privilege requirements.