T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:60
- Finding
- Unverified Remote Installation Scripts Executed Directly by Shells## Vulnerability Details **File Location**: `SKILL.md`, lines 60–64 **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 first-time setup instructions download mutable content from external OOMOL endpoints and pass it directly to Bash or PowerShell for execution. The commands provide no version pinning, cryptographic checksum validation, publisher-signature verification, or opportunity to inspect the downloaded scripts before execution. Although HTTPS protects data in transit under normal conditions, it does not establish artifact immutability. A compromise of the hosting service, publisher account, deployment pipeline, DNS or certificate trust chain could replace the installer after this Skill has been reviewed. The changed payload would then execute without further validation. Installing the `oo` CLI may be relevant to the declared connector functionality, but immediate remote-to-shell execution exceeds the minimum privilege and trust required to perform that installation. The Skill could instead direct users to a signed package or a pinned, independently verified artifact. ### Attack Path 1. The `oo` command is unavailable, causing the Agent or user to consult the first-time setup instructions. 2. An attacker compromises or otherwise gains control over the installer response from `cli.oomol.com`. 3. The user runs the documented `curl | bash` or `irm | iex` command. 4. The shell executes the attacker-controlled response immediately, without integrity or authenticity verification at the artifact level. 5. The payload performs arbitrary actions using the permissions of the account that launched the command. ### Impact Assessment Successful exploitation provide ...[truncated 907 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the `curl | bash` and `irm | iex` installation patterns. 2. Prefer an official operating-system package manager that verifies signed packages and supports explicit version selection. 3. If a standalone installer is necessary, download it to a local file rather than piping it into an interpreter. 4. Pin an exact release version and publish a cryptographic checksum through an independently controlled, authenticated channel. 5. Verify the publisher's digital signature and the pinned checksum before execution; fail closed if either check does not pass. 6. Allow the user to inspect the downloaded artifact and require explicit approval before executing it. 7. Run installation with ordinary user privileges wherever possible, requesting elevation only for a narrowly defined operation when strictly necessary. 8. Keep installation outside normal Skill execution and direct users to audited, version-specific installation documentation.