T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:57
- Finding
- Unverified Remote Installer Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 57–61 **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 download installer scripts over the network and pass their contents directly to a command interpreter. Neither command pins an immutable release nor verifies a cryptographic checksum or signature before execution. Installation of the `oo` CLI supports the Skill's declared ScraperAPI functionality, and the instructions only recommend installation after a command-not-found error. However, immediate execution of mutable remote content is not the minimum safe mechanism required to install the dependency. The effective code can change after the Skill has been audited. No evidence establishes that the currently hosted installers are malicious. Nevertheless, compromise of the hosting infrastructure, publishing account, DNS resolution, or another part of the delivery chain could turn these documented commands into an arbitrary-code-execution mechanism. ### Attack Path 1. The `oo` CLI is unavailable, causing the user or Agent to follow the first-time setup instructions. 2. An attacker compromises or gains control over the remote installer delivery path. 3. The attacker replaces the expected installer response with a malicious shell or PowerShell payload. 4. `curl | bash` or `irm | iex` executes the response immediately without integrity or authenticity verification. 5. The payload runs with the privileges of the user who invoked the installation command. ### Impact Assessment Successful exploitation permits arbitrary command execution within the invoking user's security context. The resulting scope may include access to ...[truncated 531 chars]
- Remediation
- ## Remediation Suggestions 1. Replace pipe-to-shell installation with a trusted package manager or a version-pinned official release. 2. If a standalone artifact is required, download it to disk without executing it immediately. 3. Pin the artifact to a specific version and immutable release URL. 4. Publish a SHA-256 checksum and preferably a cryptographic signature through an independently protected channel. 5. Verify the checksum and signature before execution, and abort installation on any mismatch. 6. Allow the user to inspect the downloaded installer before explicitly approving execution. 7. Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation. 8. Document the files, permissions, and configuration changes performed by the installer.
