T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:57
- Finding
- Unverified Remote Installation Scripts Are Executed Directly by the Shell<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 57-61 **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 installation instructions retrieve mutable content from `cli.oomol.com` and immediately execute it using Bash or PowerShell. The downloaded scripts are not pinned to an immutable version and are not verified using a cryptographic signature or checksum before execution. Although the hostname corresponds to the declared OOMOL service and installation is presented as a conditional first-time setup step, this design creates a remote code-execution channel whose effective payload can change after the Skill has been reviewed. It exceeds the minimum privileges necessary to document or invoke the KlickTipp connector because installation could instead use a pinned, independently verified package. The audit found no evidence that the current remote scripts are malicious. However, the package does not contain those scripts, so their contents and future behavior cannot be established from the audited artifact. ### Attack Path 1. The `oo` command is unavailable on the target system. 2. The Agent or user follows the first-time setup instructions. 3. The shell downloads the current installation script from `cli.oomol.com`. 4. The script is passed directly to Bash or PowerShell without local inspection, version pinning, checksum validation, or signature verification. 5. If the distribution endpoint, publishing account, DNS/TLS trust chain, or hosted script is compromised, attacker-controlled commands execute with the privileges of the user running the installation command. ### Impact Assessment Successful exploitation permits arbitrary command execution under the installing user's security ...[truncated 584 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Replace pipe-to-shell installation with a pinned release from an official, verifiable distribution channel. 2. Download the installer or package to a local file without executing it automatically. 3. Publish and verify a cryptographic signature or a checksum obtained through an independent trusted channel. 4. Pin the installer to an immutable version rather than retrieving the mutable latest script. 5. Prefer signed operating-system packages or package-manager distributions where available. 6. Display the exact source, version, checksum, and intended effects before installation. 7. Require explicit user approval before executing any downloaded installer. 8. Run installation with ordinary user privileges unless a specific, documented operation requires elevation. ]]>
