T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:66
- Finding
- Unverified Remote Installer Scripts Executed Directly by Shell Interpreters<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 66–70 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical ### 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 pass their contents to Bash or PowerShell. Neither command pins a specific installer version nor verifies a cryptographic signature or checksum before execution. Although installing the `oo` CLI supports the Skill's declared functionality and the download domain is consistent with the named provider, direct pipe-to-interpreter installation exceeds the minimum privileges necessary. Downloading an artifact, verifying its integrity, and obtaining approval before execution would accomplish the same purpose with substantially less supply-chain risk. Because the effective scripts are hosted remotely, their contents can change after this Skill has been reviewed. Compromise of the hosting service, installer publishing pipeline, domain, or relevant network trust path could therefore convert the documented setup procedure into an arbitrary-code-execution channel. The separate connector network behavior is disclosed and necessary to operate LiveAgent through OOMOL. The audited file contains no evidence that it reads raw credentials or covertly transmits sensitive information to an unrelated service. ### Attack Path 1. The user attempts to use the Skill on a system where the `oo` CLI is unavailable. 2. The command fails with `oo: command not found`, causing the first-time setup instructions to apply. 3. An attacker compromises or gains control over the remote installer content or its publication infrastructure. 4. The user or agent runs the documented `curl | bash` or `irm | iex` command. 5. T ...[truncated 958 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Remove the direct `curl | bash` and `irm | iex` installation patterns. 2. Direct users to a trusted package manager or an official, versioned release repository. 3. Pin the installer or package to an explicit release version. 4. Download the installer to a local file instead of executing the network response directly. 5. Publish and verify a SHA-256 checksum or, preferably, a cryptographic signature using a separately distributed trusted key. 6. Fail closed if signature or checksum verification does not succeed. 7. Allow the user to inspect the downloaded artifact and require explicit approval before executing it. 8. Run installation with ordinary user privileges wherever possible and request elevation only for specific, documented operations that require it. 9. Document the expected files, directories, subprocesses, and network endpoints used by the installer. 10. For automated environments, use a reviewed and immutable installer artifact rather than a mutable URL. ]]>
