T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installation Scripts Executed Directly by Shells## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **Vulnerability Type**: Remote payload retrieval and immediate 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 installation instructions retrieve scripts from externally controlled URLs and execute them immediately using `bash` or PowerShell's `Invoke-Expression`. No release version is pinned, and no cryptographic checksum or publisher signature is verified before execution. HTTPS protects the connection in transit but does not ensure that the script remains identical to the version reviewed during this audit. Compromise of the distribution server, hosting account, DNS infrastructure, TLS termination, or release process could cause arbitrary attacker-controlled commands to execute. Installing the `oo` CLI is relevant to first-time setup, but piping mutable network content directly into an interpreter exceeds the minimum privilege and trust necessary to accomplish that task. The audit found no evidence that the current remote scripts are malicious; the vulnerability is the unrestricted remote execution mechanism and its mutable supply-chain payload. ### Attack Path 1. The `oo` command is unavailable, causing the user or agent to follow the first-time setup instructions. 2. An attacker compromises or gains control over the remote installation endpoint or its supporting delivery infrastructure. 3. The attacker modifies `install.sh` or `install.ps1` to include malicious commands. 4. The documented command downloads the current payload without local inspection or integrity verification. 5. `bash` or `Invoke-Expression` immediately executes the attacker-controlled content. 6. The payload operates with all permissions available to the user running the ...[truncated 726 chars]
- Remediation
- ## Remediation Suggestions Replace direct pipe-to-shell and `Invoke-Expression` installation with a verifiable installation process: 1. Pin the installer or binary to a specific reviewed release rather than a mutable URL. 2. Download the artifact to a local file without executing it automatically. 3. Publish and verify a fixed SHA-256 or stronger cryptographic digest through an independently protected channel. 4. Prefer signed release artifacts and validate the publisher signature before execution. 5. Allow the user to inspect the downloaded installer before explicitly approving execution. 6. Use a trusted platform package manager where available, with repository signature validation enabled. 7. Run installation with ordinary user privileges unless a documented operation strictly requires elevation. 8. Avoid automatically invoking installation as a fallback; display secure setup instructions and require explicit user approval.