T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:63
- Finding
- Unverified Remote Installer Download and Immediate Shell Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 63-67 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical ### 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 setup instructions pipe mutable content retrieved from an external server directly into Bash or PowerShell. The downloaded installers are not pinned to a specific version, saved for inspection, or validated using a publisher signature or cryptographic checksum before execution. Although the download domain is associated with the service used by the Skill, this pattern makes the effective executable payload dependent on whatever the server returns at invocation time. The reviewed Skill therefore cannot guarantee that the executed code is the same code that existed when the Skill was audited. Installing the required CLI may support the declared TimeCamp integration, but immediate execution of an unverified response exceeds the minimum-risk installation process. Compromise of the hosting infrastructure, DNS, TLS termination, installer publication pipeline, or privileged publisher account could turn these instructions into an arbitrary-code delivery channel. ### Attack Path 1. The `oo` CLI is unavailable, causing the Agent or user to follow the first-time setup instructions. 2. An attacker compromises the installer host, publication pipeline, DNS resolution, TLS delivery infrastructure, or another component capable of controlling the HTTP response. 3. The attacker replaces or modifies `install.sh` or `install.ps1` with a malicious payload. 4. `curl | bash` or `irm | iex` forwards the response directly to a command interpreter without verification. 5. The malicious payload executes with the privileges of the Agent or user running the installation c ...[truncated 969 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the direct `curl | bash` and `irm | iex` installation instructions. 2. Prefer a trusted platform package manager that validates publisher signatures and package integrity. 3. If a standalone installer is required, pin it to an immutable, explicitly identified release rather than a mutable generic installation URL. 4. Download the installer to a local file without executing it. 5. Publish an expected SHA-256 digest through an independently protected release channel and verify it before execution. 6. Cryptographically sign release artifacts and validate the signature against a pinned, documented publisher key. 7. Allow the user to inspect the downloaded installer and request explicit approval before running it. 8. Execute installation with standard user privileges unless a specific, documented operation strictly requires elevation. 9. Document the exact files, directories, network endpoints, and configuration changes made by the installer. 10. Fail closed if checksum, signature, version, or origin validation fails; do not fall back to executing an unverified response.