T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:82
- Finding
- Unverified Remote Installation Scripts Executed Directly by Shell## Vulnerability Details **File Location**: `SKILL.md`, lines 82–86 **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 Both installation commands retrieve mutable content from a remote server and immediately pass the response to a command interpreter. The downloaded scripts are not pinned to a specific version, saved for inspection, or validated using a cryptographic signature or checksum. Consequently, the code executed on a user's computer can differ from the content available when this Skill was audited. Although installing the `oo` CLI supports the declared Metabase functionality and the download domain is consistent with OOMOL branding, immediate execution of an unverified network response is not the minimum privilege or safest installation mechanism necessary to provide that functionality. The effective payload could be changed through compromise of the hosting service, publishing credentials, release pipeline, DNS infrastructure, or another part of the delivery path. An unexpected HTTP response could likewise be interpreted as shell code. ### Attack Path 1. The `oo` CLI is unavailable, causing the agent or user to consult the first-time setup instructions. 2. An attacker compromises the remote script, its publishing pipeline, or a trusted component of the delivery infrastructure. 3. The macOS/Linux command streams the current response directly into `bash`, or the Windows command sends it directly to `Invoke-Expression`. 4. The unverified response executes with the privileges of the user running the installation. 5. The payload can access resources available to that user and may install additional components or establish persistence, depending on local permissio ...[truncated 609 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the pipe-to-shell and `Invoke-Expression` installation patterns. 2. Direct users to a version-pinned package from an authenticated official release channel. 3. Download the installer to a local file without executing it automatically. 4. Publish a cryptographic checksum and preferably a signed release manifest, then require verification before execution. 5. Allow users to inspect the downloaded installer and run it as a separate, explicit step. 6. Document the files, permissions, and system changes made by the installer. 7. Avoid requesting administrative privileges unless a specific installation operation requires them. 8. Prefer platform package managers that provide package signing, version pinning, and integrity verification.