T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:58- Finding
Unverified Remote Installer Execution Through Shell Pipelines
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 58–62
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighThe first-time setup instructions download installation scripts from a mutable external URL and immediately execute the responses:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
Both installation methods combine network retrieval and code execution in a single pipeline. The downloaded scripts are not version-pinned, saved for inspection, checked against a cryptographic digest, or verified using a trusted digital signature.
HTTPS protects the connection in transit but does not establish that the current response is the same payload that existed when the Skill was audited. Compromise of the hosting service, publishing account, DNS or certificate trust chain could therefore replace the installer with arbitrary code.
Installing the CLI may be necessary when it is absent, but immediate execution of an unverified remote response exceeds the minimum privileges needed to provide installation guidance. The Skill could instead direct the user to a pinned, independently verifiable package. The PowerShell command presents the same underlying vulnerability as the Bash command.
Attack Path
- A user requests a Cincopa operation through the Skill.
- The required
ooCLI is unavailable, causing the Agent or user to follow the first-time setup instructions. - An attacker compromises or gains control over the remote installer response or its delivery infrastructure.
curlorirmretrieves the attacker-controlled response.- The pipeline passes the response directly to Bash or
Invoke-Expressionwithout verification or inspection. - The malicious response executes with the privileges of the account running the install ...[truncated 677 chars]
- Remediation
View remediation
Remediation Suggestions
-
Remove both direct pipe-to-shell installation commands.
-
Use a version-pinned release artifact or a trusted operating-system package manager.
-
Download the installer to a local file without executing it immediately.
-
Validate the artifact using a publisher signature or a cryptographic checksum obtained through an independently trusted channel.
-
Allow the user to inspect the downloaded file and require explicit approval before execution.
-
Document the exact files, permissions, and system changes performed by the installer.
-
Run installation with ordinary user privileges unless a specific, documented operation requires elevation.
-
Prefer instructions resembling the following verified workflow:
bash curl -fL -o oo-install.sh https://trusted.example/path/to/versioned/oo-install.sh echo '<expected-sha256> oo-install.sh' | sha256sum --check - less oo-install.sh bash oo-install.sh -
Apply an equivalent download, signature-validation, review, and separate-execution workflow on Windows rather than using
Invoke-Expression.
-
