T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installer Scripts Executed Directly by Shell Interpreters## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High ```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 execute them using Bash or PowerShell. The downloaded content is not pinned to a specific release and is not subjected to checksum verification, cryptographic signature validation, or user inspection before execution. HTTPS protects the connection in transit when its trust assumptions hold, but it does not establish that the script is immutable or safe. If the hosting account, web server, CDN, DNS resolution, certificate infrastructure, or release process is compromised, the remotely served installer can be replaced after the Skill has been reviewed. This installation mechanism grants the remote response the full privileges of the user running the command. Installing a CLI through unrestricted shell execution also exceeds the minimum privileges needed for the Skill's declared read-only Airmeet operations. CLI installation should instead be treated as an independently trusted and explicitly approved prerequisite. The Skill's ordinary `oo connector schema` and `oo connector run` operations necessarily transfer request and response data through the declared OOMOL/Airmeet connector. The audited file does not show credential harvesting or transmission to an unrelated endpoint; the confirmed issue is the unverified execution of the installer payloads. ### Attack Path 1. The `oo` CLI is unavailable, causing the setup instructions to become applicable. 2. An attacker compromises or otherwise gains control over the installer delivery path, such as the hosting service, publishing account, DNS, CDN, or build/release pipeline. ...[truncated 1101 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the direct `curl | bash` and `irm | iex` installation commands from Agent-executable instructions. 2. Treat CLI installation as a manual prerequisite requiring explicit user approval rather than an automatic fallback action. 3. Prefer a trusted operating-system package manager or a signed official release package pinned to a specific version. 4. If script-based installation remains necessary: - Download the script to a local file without executing it. - Pin the download to an immutable, versioned release URL. - Publish and verify a cryptographic checksum obtained through a separately protected channel. - Cryptographically sign releases and verify the signature against a documented trusted key. - Allow the user to inspect the script before execution. - Execute it with the least-privileged account possible and avoid privilege elevation unless strictly necessary. 5. Document the files, permissions, network access, and system changes made by the installer. 6. For Windows, replace `irm ... | iex` with a download, signature-verification, review, and explicit-execution workflow equivalent to the hardened Unix process.