T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:68- Finding
Unverified Remote Shell Script Execution on macOS and Linux
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:68
Vulnerability Type: Remote payload retrieval and immediate shell execution
Risk Level: HighComplete Code Snippet:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction pipes a remotely downloaded script directly into
bash. The payload is retrieved from a mutable URL without a pinned version, cryptographic signature verification, checksum validation, or an opportunity to inspect the downloaded file before execution.HTTPS protects the connection in transit but does not guarantee that the server, deployment pipeline, domain, or current script contents are trustworthy. Because the effective payload can change after the Skill has been reviewed, compromise of the remote endpoint or its publishing infrastructure could turn this instruction into arbitrary code execution.
Installing the CLI may be relevant to the declared Streamtime connector functionality, but direct execution of an unverified remote script exceeds the minimum privileges and trust required to provide installation guidance.
Attack Path
- The
ooCLI is unavailable and an action fails withoo: command not found. - The agent or user follows the documented first-time setup instruction.
curlretrieves the current contents ofhttps://cli.oomol.com/install.sh.- The pipe sends those contents directly to
bashwithout local verification. - A compromised or malicious remote payload executes with the permissions of the invoking account.
- The payload can perform any operation available to that account, including reading accessible data, modifying files, installing additional software, or retrieving further payloads.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking user's privileges. The accessible scope may include local project files, user- ...[truncated 367 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashexecution pattern. - Pin installation instructions to a specific, immutable CLI release and version.
- Download the installer or release artifact to a local file without executing it.
- Verify a publisher-provided cryptographic signature or a securely distributed, pinned SHA-256 checksum.
- Prefer an authenticated operating-system package manager or an official signed release package.
- Allow inspection of the downloaded artifact before installation.
- Execute installation with ordinary user privileges unless elevated access is demonstrably necessary.
- Document the files, network access, and permissions required by the installer.
- Remove the direct
