T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:56- Finding
Unverified Remote Shell Script Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 56
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction downloads a mutable script from an external URL and pipes it directly into Bash. The script is executed without version pinning, checksum verification, cryptographic signature validation, or an opportunity to inspect the downloaded content.
The HTTPS connection protects data in transit under normal conditions, but it does not establish that the current script is the same artifact that was reviewed. Compromise of the remote server, publishing account, domain, certificate infrastructure, or build pipeline could change the effective payload after the Skill has been audited.
Attack Path
- The
ooCLI is absent, causing the documented first-time setup condition to apply. - An Agent or user follows the installation instruction.
curlretrieves the current content ofhttps://cli.oomol.com/install.sh.- The pipeline passes that content directly to Bash without integrity validation or review.
- Bash executes every command supplied by the remote endpoint with the privileges of the invoking user.
- A compromised installer can access user-readable files, modify writable files, invoke other installed programs, make additional network requests, or establish persistence where the user's permissions allow it.
Impact Assessment
Successful exploitation provides arbitrary command execution with the privileges of the account running the command. This may expose credentials and user data accessible to that account, alter project or shell configuration files, install additional software, and enable further payload retrieval. If the command is run from an elevated shell, the impact could extend to system-wide compromise; ...[truncated 55 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Do not pipe network responses directly into a shell.
- Refer to a specific, immutable CLI release rather than a mutable installation endpoint.
- Download the installer or binary to a local file without executing it.
- Verify a publisher-provided cryptographic signature or a checksum obtained through a trusted, independent release channel.
- Allow the user to inspect the artifact before execution.
- Require explicit user approval immediately before running the verified installer.
- Run installation with ordinary user privileges unless elevated privileges are demonstrably necessary.
- Prefer a trusted package manager or signed release package with provenance and reproducible release metadata.
