T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installer Download and Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **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 first-time setup instructions retrieve mutable scripts from an external URL and immediately execute them through Bash or PowerShell. Neither installation path pins a specific artifact version, verifies a cryptographic checksum or publisher signature, nor gives the user an opportunity to inspect the downloaded script before execution. HTTPS protects the network connection but does not establish that every future version of the remotely hosted script is safe. The effective executable payload can change after this Skill has been reviewed. Compromise of the hosting infrastructure, publication process, domain, DNS resolution, or applicable TLS trust chain could therefore turn the documented installation commands into an arbitrary-code execution channel. Installing the `oo` CLI supports the declared BigCommerce connector functionality, but immediate execution of an unverified remote script exceeds the minimum necessary installation behavior. A pinned and cryptographically verified release artifact would provide the required functionality with lower supply-chain risk. ### Attack Path 1. The user or agent attempts a BigCommerce action and receives an `oo: command not found` error. 2. The agent follows the first-time setup instructions in `SKILL.md`. 3. An attacker compromises or gains control over the remote installer delivery or publication path. 4. The attacker replaces the installer response with malicious shell or PowerShell commands. 5. `curl | bash` or `irm | iex` executes the response immediately without integrity verification. 6. The malicious c ...[truncated 1057 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the direct `curl | bash` and `irm | iex` execution pipelines. 2. Prefer an authenticated operating-system package manager or an official, versioned release package. 3. Pin the CLI to a reviewed version and use an immutable or version-specific artifact URL. 4. Download the artifact to disk without executing it automatically. 5. Verify a publisher signature or compare a SHA-256 digest against a trusted, independently distributed value before execution. 6. Present the resolved version, source, checksum, and intended installation changes to the user and obtain explicit approval before running the installer. 7. Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation. 8. Document how users can inspect the installer and verify its provenance manually. 9. Consider making CLI installation an administrator-controlled prerequisite rather than an action performed by the Skill.