T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:18- Finding
Unverified Remote Installation Script Executed Directly by Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:18
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalbash curl -fsSL https://ollama.ai/install.sh | shTechnical Analysis
The command retrieves a mutable script from an external URL and immediately passes its contents to
sh. The payload is not pinned to a version, saved for inspection, or verified using a cryptographic signature or fixed checksum. Consequently, the code that executes can differ from the code available when the Skill was audited.HTTPS protects the connection in transit but does not mitigate compromise of the hosting service, its deployment pipeline, DNS or account credentials. It also does not protect users if the remote endpoint intentionally changes the script.
This installation behavior is related to the declared Ollama setup function, but direct pipe-to-shell execution is not necessary. A verified package or a separately downloaded and authenticated release artifact would provide the same functionality with lower risk.
Attack Path
- An attacker compromises the external installation endpoint, its publishing account, or its release pipeline.
- The attacker modifies
install.shto include arbitrary shell commands. - A user follows the Skill instructions and runs the documented command.
curlretrieves the attacker-controlled response and passes it directly tosh.- The malicious commands execute with the privileges of the invoking user. If the script invokes
sudo, is run from a privileged shell, or exploits local installation privileges, the impact can extend to the entire host.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking account. Potential consequences include modification of user files, theft of accessible credentials or model data, installation of additional payloads, and compromise of later fleet operations. Execution ...[truncated 139 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not pipe a network response directly into a shell.
- Pin installation to a specific, reviewed Ollama release.
- Download the artifact to a local file before execution.
- Verify a publisher signature or a hard-coded SHA-256 checksum obtained through an independent trusted channel.
- Display or inspect the downloaded script before running it.
- Prefer signed operating-system packages or other authenticated release artifacts.
- Execute installation with ordinary user privileges wherever possible, elevating only narrowly scoped operations that require administrative access.
