T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:97
- Finding
- Unverified Remote Installer Scripts Are Executed Directly## Vulnerability Details **File Location**: `SKILL.md`, lines 97–101 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical The first-time setup instructions download mutable scripts from an external server and immediately execute them: ```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 Both installation commands connect a network retrieval operation directly to a command interpreter. The downloaded content is not pinned to a specific release and is not checked against a cryptographic signature or checksum before execution. Consequently, the code ultimately executed can change after the Skill has been reviewed. HTTPS protects the connection in transit under normal conditions, but it does not mitigate compromise of the hosting service, publication pipeline, CDN, DNS infrastructure, or vendor account. Any party able to alter the remote installer can supply arbitrary shell or PowerShell commands. Installing the CLI when it is absent may be relevant to the declared Google Drive connector functionality. However, immediate execution of unverified remote content exceeds the minimum privilege and trust required to perform that installation. A separately downloaded, version-pinned, cryptographically verified package would provide the required functionality with substantially lower risk. ### Attack Path 1. The `oo` CLI is unavailable, causing an `oo: command not found` error. 2. The Agent follows the documented first-time setup instructions. 3. An attacker compromises or gains control over the installer hosting service, deployment pipeline, CDN, DNS path, or other mechanism capable of changing the response. 4. The attacker replaces the expected installer with a malicious shell or PowerShell payload. 5. `curl` or `irm` retrieves the attacker-contro ...[truncated 876 chars]
- Remediation
- ## Remediation Suggestions 1. Remove both direct execution patterns (`curl | bash` and `irm | iex`). 2. Distribute the CLI through a trusted package manager or a versioned release hosted in the official project repository. 3. Pin installation instructions to a specific release rather than a mutable installer URL. 4. Download the package or script to a local file without executing it. 5. Publish a cryptographic checksum or, preferably, a signed release manifest through an independently protected channel. 6. Verify the checksum and signature before installation, and abort on any mismatch. 7. Allow the user or Agent to inspect the downloaded script before execution. 8. Execute the installer with ordinary user privileges unless a specific installation step demonstrably requires elevation. 9. If elevated privileges are required, isolate and document the exact command that needs them rather than running the complete remote installer as an administrator. 10. Document the external domains contacted and the data handled by the OOMOL connector so users can make an informed trust decision.