T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:69
- Finding
- Unverified Remote Installer Scripts Are Executed Directly## Vulnerability Details **File Location**: `SKILL.md:69-73` **Vulnerability Type**: Remote payload retrieval and immediate execution **Risk Level**: High ### Complete Code Snippet ```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 setup instructions retrieve mutable scripts from `cli.oomol.com` and immediately execute their contents in 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 script. Consequently, the effective code executed on a user's system can change after the Skill has been reviewed. HTTPS protects the connection in transit but does not protect against compromise of the hosting infrastructure, malicious modification of the installer, loss of control over the domain, or unauthorized publication. Installing the CLI may be necessary for the declared functionality, but executing an unverified remote script is not the minimum privilege or safest installation method required to provide that functionality. ### Attack Path 1. The `oo` command is unavailable on the user's system. 2. The Skill follows its first-time setup instructions. 3. An attacker compromises the installer host, publication process, or other trusted delivery infrastructure. 4. The attacker replaces the installer response with arbitrary shell commands. 5. `bash` or PowerShell executes the response immediately under the invoking user's privileges. 6. The payload can alter the host before installing—or pretending to install—the expected CLI. ### Impact Assessment Successful exploitation provides arbitrary command execution with the privileges of the user running the installation. Depending on those privileges and the host configuration, an attacker could: - ...[truncated 318 chars]
- Remediation
- ## Remediation Suggestions - Do not pipe downloaded content directly into a shell or use `Invoke-Expression`. - Direct users to a version-pinned package or release artifact from a verifiable source. - Download the installer to a local file before execution. - Publish and verify a SHA-256 or stronger checksum over the downloaded artifact. - Prefer cryptographic signature verification using a separately distributed trusted public key. - Display the resolved version, source, checksum, and intended installation paths before requesting explicit user approval. - Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation. - Recommend platform package managers with signature and provenance controls where available.