T03 · Remote Payload Retrieval and Execution
- Location
scripts/install.sh:35- Finding
Unsafe Remote Installer Execution Recommendation
- Content
View full analysis
/dev/null; then echo "❌ 错误:需要 uv 包管理器" echo " 安装:curl -LsSf https://astral.sh/uv/install.sh | sh" exit 1 fi ``` ### Technical Analysis The installer does not execute this command automatically, but it instructs users to download mutable content from an external URL and pipe it directly into `sh`. The downloaded script is not pinned to a version, inspected, signature-verified, or checked against a cryptographic digest. Although `astral.sh` is related to the legitimate `uv` project, direct remote-to-shell execution means the effective code can change after this Skill has been audited. Compromise of the remote host, its deployment pipeline, DNS resolution, or the network trust chain could result in arbitrary replacement code being executed. ### Attack Path 1. A user runs `scripts/install.sh` without `uv` installed. 2. The installer prints the `curl ... | sh` command as the prescribed installation method. 3. The user copies and executes the command. 4. `curl` retrieves the current, unaudited response from the external host. 5. The response is immediately interpreted by the local shell. 6. A compromised or replaced response executes arbitrary commands with the user's privileges. ### Impact Assessment Successful exploitation provides arbitrary command execution as the account running the installation command. The payload could access that user's files, OpenClaw configuration, Feishu credentials, environment variables, and any other resources available to the account. It does not inherently grant root privileges unless the user executes it as root or the payload chains another privilege-escalation flaw. ]]>- Remediation
View remediation
