T03 · Remote Payload Retrieval and Execution
- Location
scripts/raon.sh:343- Finding
Remote installation script executed through a shell pipeline
- Content
View full analysis
/dev/null; then echo -e "${YELLOW}Ollama 미설치 — 자동 설치 시도...${NC}" if command -v brew &>/dev/null; then brew install ollama && echo -e "${GREEN}✅ Ollama 설치 완료${NC}" else echo -e "${YELLOW}Homebrew 미설치. 아래 명령어로 수동 설치하세요:${NC}" echo " curl -fsSL https://ollama.ai/install.sh | sh" exit 1 fi fi ``` ### Technical Analysis The `install-model` workflow instructs users to pipe a mutable network response directly into a shell. Although the command is displayed rather than automatically executed, it is part of the documented installation path presented by the Skill. TLS protects the connection in transit but does not make the downloaded script immutable. The effective code can change after this package has been audited. Compromise of the remote origin, CDN, DNS path, or publication account could consequently turn this installation step into arbitrary code execution. The downloaded content is not pinned to a version and is not verified using a checksum or digital signature. ### Attack Path 1. A user runs the `install-model` command on a system without Ollama or Homebrew. 2. The Skill displays `curl -fsSL https://ollama.ai/install.sh | sh` as the installation procedure. 3. The user copies and executes the command. 4. The current remote response is passed directly to the local shell. 5. If the remote source or delivery path has been compromised, attacker-controlled commands run with the invoking user's privileges. ### Impact Assessment A malicious remote script could: - Read or modify all files accessible to the invoking user. - Read credentials stored under the user's home directory. - Install persistence mechanisms. - Download and execute additional payloads. - Modify shell profiles or local development tools. - Ex ...[truncated 219 chars]- Remediation
View remediation
