T03 · Remote Payload Retrieval and Execution
Error
- Location
- references/api-guide.md:182
- Finding
- Unverified Remote Installer Executed Directly by a Shell<![CDATA[ ## Vulnerability Details **File Location**: `references/api-guide.md:182` **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical ### Vulnerable Code ```text | `uv run` fails | uv not installed or Python < 3.11 | Install uv: `curl -LsSf https://astral.sh/uv/install.sh \| sh` | ``` ### Technical Analysis The troubleshooting documentation instructs users to download a remote installation script and pipe it directly into `sh`. The fetched payload is executed immediately without: - Pinning it to an immutable version. - Verifying a checksum or cryptographic signature. - Saving and inspecting the script before execution. - Constraining the permissions available to the installer. Although the referenced domain appears associated with the legitimate `uv` project, the effective payload remains mutable after the Skill has been reviewed. Security therefore depends on the continued integrity of the domain, DNS resolution, TLS infrastructure, hosting environment, and upstream release process. Installing `uv` is a prerequisite rather than part of image generation itself. Blind execution of a remote script is not the minimum privilege or minimum trust necessary to satisfy that prerequisite. ### Attack Path 1. A user encounters the documented `uv run` troubleshooting entry. 2. The user copies and executes the recommended command. 3. The shell retrieves the current contents of the remote URL. 4. A compromised hosting account, upstream release process, DNS path, or TLS trust chain supplies modified shell code. 5. The pipe passes that code directly to `sh` without inspection or integrity verification. 6. The malicious code executes with all permissions held by the invoking user. ### Impact Assessment A malicious installer could execute arbitrary commands with the invoking user's privileges. Depending on that user's access, it could: - Read, alter, or delete user-accessible files. - Access environment variables, credentials, A ...[truncated 435 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions Remove the `curl | sh` installation instruction. Prefer one of the following approaches: 1. Recommend installation through a trusted operating-system package manager where available. 2. Direct users to the official installation documentation rather than embedding an immediately executable pipeline. 3. If a standalone installer is necessary: - Pin an explicit installer or release version. - Download it as a separate file. - Obtain the expected checksum or signature through an authenticated channel. - Verify the checksum or signature before execution. - Allow the user to inspect the downloaded file. - Run it without elevated privileges unless elevation is demonstrably required. 4. Document the files and directories the installer is expected to modify. 5. For reproducible environments, provide a version-pinned dependency setup with integrity hashes. ]]>
