T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:57
- Finding
- Unverified Remote Installation Scripts Executed Directly by Shells## Vulnerability Details **File Location**: `SKILL.md`, lines 57–61 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical ```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 download mutable scripts from external URLs and immediately execute their contents with Bash or PowerShell. They do not pin a reviewed release, verify a cryptographic signature or checksum, save the script for inspection, or otherwise validate its integrity before execution. Although `cli.oomol.com` is consistent with the declared OOMOL provider, domain consistency does not eliminate the risks of server compromise, DNS or delivery-chain compromise, publishing-account compromise, or a future modification of the remotely hosted scripts. The effective executable payload can change after this Skill has been audited. Installing the CLI is ancillary to the Skill's declared Botpress read functionality. Allowing an unverified response to execute with all permissions of the current user therefore exceeds the minimum privilege and trust necessary to provide setup guidance. ### Attack Path 1. The `oo` CLI is absent, causing an agent or user to follow the first-time setup instructions. 2. An attacker compromises the remote installation endpoint or its publishing infrastructure, or otherwise causes it to return attacker-controlled script content. 3. `curl` or `Invoke-RestMethod` retrieves the mutable payload. 4. The shell pipeline passes the response directly to Bash or `Invoke-Expression` without integrity verification or review. 5. The attacker-controlled script executes immediately with the privileges of the user running the command. 6. The payload can inspect accessible files and credentials, alter the host, install additional software, or transmi ...[truncated 831 chars]
- Remediation
- ## Remediation Suggestions - Remove both pipe-to-shell installation commands. - Direct users to a trusted platform package manager or a manually downloadable, versioned release artifact. - Pin installation instructions to a specific reviewed CLI version rather than a mutable latest-version script. - Publish cryptographic checksums and signed release artifacts through an independently verifiable channel. - Require users to download the artifact first, verify its signature and checksum, and only then execute or install it. - If an installation script remains necessary, save it locally for inspection instead of piping it directly into a shell. - Document that installation must occur without administrator privileges unless a specific, justified operation requires elevation. - Apply the same controls to both the Bash and PowerShell installation paths.