T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:60- Finding
Unverified Remote Installer Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 60–64
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: CriticalComplete vulnerable code snippet:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The first-time setup instructions pipe network responses directly into Bash or PowerShell. Neither command pins a reviewed installer version nor verifies a cryptographic signature or checksum before execution. The effective code can therefore change after the Skill package has been reviewed.
HTTPS protects the connection in transit under ordinary conditions, but it does not protect against compromise of the remote publication infrastructure, unauthorized modification of the hosted installer, or malicious changes by an entity controlling the endpoint. The commands also provide no opportunity to inspect the downloaded content before executing it.
Installing the
ooCLI is relevant when the required executable is unavailable, and the instructions place installation in a conditional fallback path. Nevertheless, immediate execution of an unverified remote response exceeds the minimum safe mechanism necessary to install the dependency.Attack Path
- A football-data.org action is requested while the
ooexecutable is unavailable. - The attempted command fails with an
oo: command not founderror. - The first-time setup path is followed.
curlorInvoke-RestMethodretrieves the current installer from the remote OOMOL endpoint.- Bash or
Invoke-Expressionexecutes the response without integrity or authenticity verification. - If the endpoint, publishing account, or delivery infrastructure has been compromised, attacker-controlled commands execute with the privileges and environmental access of the invoking use ...[truncated 1004 chars]
- A football-data.org action is requested while the
- Remediation
View remediation
Remediation Suggestions
- Remove both pipe-to-shell installation commands.
- Pin installation instructions to a specific, reviewed
ooCLI release rather than a mutable installer URL. - Download the artifact to a local file without executing it immediately.
- Publish a cryptographic signature or SHA-256 checksum through an independently protected channel and verify it before execution.
- Prefer a trusted operating-system package manager or signed platform package where available.
- Display the artifact source, pinned version, destination, and requested privileges before installation.
- Require explicit user approval before downloading or executing an installer.
- Run installation with ordinary user privileges unless elevated privileges are demonstrably necessary.
- If an installer script remains necessary, present separate download, verification, inspection, and execution commands, and fail closed when verification is unsuccessful.
