T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:62
- Finding
- Unverified Remote Installation Scripts Are Executed Directly## Vulnerability Details **File Location**: `SKILL.md`, lines 62–66 **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 scripts from an external server and pass their contents directly to a command interpreter. Neither installation path pins a specific release nor verifies a cryptographic signature or checksum before execution. Consequently, the effective code executed by these commands can change after the Skill has been reviewed. Although the scripts are hosted on an apparently vendor-related HTTPS domain, HTTPS alone does not protect against compromise of the vendor server, deployment pipeline, CDN, DNS infrastructure, or publishing credentials. It also does not establish that a subsequently modified script matches the version audited by the user. This behavior is not required for normal SheetDB operations when the CLI is already installed. For initial installation, it also exceeds the minimum safe behavior because the remote response can be downloaded and verified without immediately executing it. ### Attack Path 1. The `oo` CLI is absent, causing an `oo: command not found` error. 2. A user or agent follows the first-time setup instructions in `SKILL.md`. 3. An attacker compromises the remote script host, its delivery infrastructure, or its release pipeline and replaces the installation response with malicious code. 4. `curl | bash` or `irm | iex` passes the response directly to the local shell without integrity or authenticity verification. 5. The malicious script executes with all permissions held by the user who initiated installation. ### Impact Assessment Successful exploitation provides arbitrary command execut ...[truncated 642 chars]
- Remediation
- ## Remediation Suggestions - Remove both direct pipe-to-shell installation commands. - Prefer an official operating-system package manager or a signed, version-pinned release package. - Pin the installer or CLI to an explicit version rather than retrieving a mutable installation endpoint. - Download the artifact to a local file without executing it automatically. - Publish and verify a cryptographic signature using a trusted public key. If signatures are unavailable, verify a checksum obtained through a separately authenticated channel. - Present the artifact version, source, checksum, and intended effects to the user and obtain explicit approval before execution. - Run installation with ordinary user privileges unless a documented installation step strictly requires elevation. - Consider sandboxing the installer and documenting the files, network destinations, and configuration changes it is expected to create.