T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:60
- Finding
- Unverified Remote Installer Download and Immediate Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 60–64 **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 installation instructions retrieve mutable scripts from `cli.oomol.com` and immediately execute their contents through Bash or PowerShell. Neither command gives the user an opportunity to inspect the downloaded code before execution. No pinned release, cryptographic checksum, digital signature, or other integrity verification is specified. Although the download domain is consistent with the declared OOMOL service, relying on HTTPS and domain ownership alone does not establish the integrity of the script over time. The effective code executed by this Skill can change after the Skill itself has been reviewed. Compromise of the vendor's hosting environment, release process, DNS infrastructure, TLS credentials, or installer endpoint could turn these commands into an arbitrary-code-execution delivery mechanism. Installing the required CLI can be legitimate, but piping a network response directly into an interpreter exceeds the minimum behavior necessary to perform installation. Downloading a pinned artifact, verifying it, and executing it separately would provide the same functionality with substantially less risk. ### Attack Path 1. The user or Agent attempts to use the Skill on a system where the `oo` CLI is unavailable. 2. Following the first-time setup instructions, it invokes one of the documented installer pipelines. 3. The command retrieves the current installer response from `cli.oomol.com`. 4. An attacker who has compromised the installer endpoint, its publishing process, or the relevant network trust infrastructure substitutes malicious script content. 5. Bash or PowerShell execut ...[truncated 1167 chars]
- Remediation
- ## Remediation Suggestions 1. Remove both direct download-to-interpreter pipelines. 2. Publish versioned installer artifacts at an official, immutable release location. 3. Pin the installation instructions to a specific reviewed CLI version rather than retrieving a mutable latest script. 4. Download the installer or binary to a local file without executing it. 5. Publish and require verification of a cryptographic signature from a documented vendor signing key. If signatures are unavailable, provide a hard-coded SHA-256 digest over the pinned artifact. 6. Execute the verified local artifact only after integrity validation succeeds. 7. Prefer a trusted platform package manager with signed metadata and version pinning where available. 8. Do not request administrator privileges unless a documented installation step strictly requires them. 9. If script-based installation must remain available, instruct users to inspect the downloaded file before execution and fail closed when signature or checksum validation fails. A safer conceptual workflow is: ```bash curl -fL -o oo-installer.sh "https://trusted.example/releases/oo/VERSION/install.sh" echo "EXPECTED_SHA256 oo-installer.sh" | sha256sum --check - less oo-installer.sh bash ./oo-installer.sh ``` The actual URL, version, digest, and signing process must come from a verified official release and must not use placeholders.