T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:58
- Finding
- Unverified Remote Installer Download and Execution<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 58–62 **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 The setup instructions download mutable scripts from `cli.oomol.com` and immediately execute them through Bash or PowerShell. There is no version pinning, manual inspection step, cryptographic signature validation, or checksum verification between retrieval and execution. Consequently, the code that ultimately runs is not the code reviewed in this skill package and can change at any time. Compromise of the hosting service, its deployment process, domain or DNS controls, or the applicable TLS trust chain could turn these installation commands into an arbitrary-code-execution channel. Installing a CLI can be legitimate, but immediate execution of an unverified remote response is not required for the skill's declared read-only Grafana Cloud operations. It exceeds the minimum privileges necessary to document or invoke those operations. ### Attack Path 1. The `oo` CLI is unavailable, causing the agent or user to consult the first-time setup instructions. 2. The agent or user executes one of the documented installation commands. 3. The command retrieves the current installer response from `cli.oomol.com`. 4. Bash or PowerShell executes the response without first authenticating its contents against a pinned release. 5. If the distribution channel or hosted script has been compromised, attacker-controlled commands execute with the privileges of the invoking user. 6. Those commands can access files and credentials available to that user, modify the user's environment, install persistence where permissions allow, or invoke additional payloads. ### Impact Assessment Successful exploitation ...[truncated 653 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Remove the direct `curl | bash` and `irm | iex` installation patterns. 2. Direct users to a version-pinned release hosted on an authenticated official release channel. 3. Download the installer or binary to a local file without executing it immediately. 4. Publish a cryptographic signature or strong checksum through an independently protected channel and require verification before execution. 5. Prefer signed platform-native packages, such as notarized macOS packages, signed Windows installers, or signed Linux repository packages. 6. Display the exact version, source URL, checksum, permissions, and intended changes before requesting explicit user approval. 7. Execute installation with ordinary user privileges unless a specific operation demonstrably requires elevation. 8. Keep installation separate from normal skill execution and never install software automatically in response to an ordinary Grafana Cloud request. A safer Unix-style workflow would resemble: ```bash curl -fSLo oo-installer.sh \ https://example.invalid/releases/vX.Y.Z/install.sh echo "<published-sha256> oo-installer.sh" | sha256sum --check less oo-installer.sh bash oo-installer.sh ``` The release URL and checksum must be replaced with authenticated, version-pinned values maintained by the publisher. Windows instructions should provide equivalent signature or checksum verification before invoking the downloaded file. ]]>