T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:72
- Finding
- Unverified Remote Installer Execution Through Shell Pipelines## Vulnerability Details **File Location**: `SKILL.md`, lines 72–76 **Vulnerability Type**: `T03: Remote Payload Retrieval and Execution` **Risk Level**: Critical ```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 external URLs and immediately execute their contents using `bash` or PowerShell's `Invoke-Expression`. No release version is pinned, and the instructions provide no checksum verification, cryptographic signature validation, or opportunity to inspect the downloaded files before execution. HTTPS protects the connection in transit when its trust assumptions hold, but it does not establish that the current server-side script is the same artifact that was reviewed. Compromise of the hosting service, publishing account, DNS infrastructure, TLS trust path, or installer build pipeline could therefore replace the effective payload after this Skill has been audited. Installing a required CLI can be legitimate, and these commands are only presented as a fallback when `oo` is unavailable. However, direct download-to-shell execution exceeds the minimum privilege and integrity requirements necessary to install that CLI safely. ### Attack Path 1. The `oo` command is unavailable, causing the Skill to use its first-time setup instructions. 2. An attacker compromises or gains control over the installer endpoint, its deployment pipeline, or another component capable of changing the returned script. 3. The agent retrieves the attacker-controlled response from `cli.oomol.com`. 4. The pipeline passes the response directly to `bash` or `Invoke-Expression` without integrity validation. 5. The malicious script executes with the permissions of the account running the agent. 6. The script can access or alter resources availa ...[truncated 943 chars]
- Remediation
- ## Remediation Suggestions - Remove both direct download-to-shell pipelines. - Pin installation to a specific reviewed CLI version rather than a mutable installer endpoint. - Download the installer or package to a local file without executing it automatically. - Verify a vendor-provided cryptographic signature or a SHA-256 digest obtained through a separately trusted, immutable release channel. - Abort installation if verification fails; never silently continue with an unverified artifact. - Prefer signed packages distributed through the operating system's standard package manager or an authenticated release repository. - Display the resolved version, source URL, verification result, and intended installation changes before execution. - Require explicit user approval before running an installer. - Execute installation with ordinary user privileges where possible and request elevation only for a narrowly defined operation when strictly necessary. - Document a manual installation procedure so users can inspect the artifact before execution.