T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:39
- Finding
- Unverified Remote Installer Piped Directly to Bash<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, line 39 **Vulnerability Type**: `T03: Remote Payload Retrieval and Execution` **Risk Level**: High ### Vulnerable Code ```bash curl -L https://foundry.paradigm.xyz | bash ``` ### Technical Analysis The installation instructions download a mutable response from an external URL and immediately execute it with Bash. The response is not pinned to a specific version, saved for inspection, or verified using a cryptographic checksum or signature. HTTPS authenticates the connection to the responding server but does not guarantee that the retrieved script is immutable or safe. Compromise of the distribution host, a redirect destination, the upstream deployment process, or the relevant network trust infrastructure could cause attacker-controlled shell commands to be returned and executed. Direct remote execution is not required for the Skill's declared purpose of setting up a Solidity project. A version-pinned and cryptographically verified Foundry release would provide the necessary functionality with substantially lower supply-chain risk. ### Attack Path 1. An attacker compromises the remote installer host, its deployment pipeline, a redirect target, or another relevant distribution component. 2. The attacker changes the response from `https://foundry.paradigm.xyz` to include malicious shell commands. 3. A user or Agent follows the Skill's Foundry installation instructions. 4. `curl -L` retrieves the attacker-controlled response, including any redirected content. 5. The shell pipeline passes the response directly to Bash without inspection or integrity verification. 6. Bash executes the payload with the privileges and environment of the invoking account. 7. The payload can access data available to that account and modify resources writable by it. ### Impact Assessment Successful exploitation provides arbitrary command execution under the invoking user's privileges. The resulting scope can includ ...[truncated 672 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions Replace the `curl | bash` pipeline with a controlled installation procedure: 1. Select and pin a reviewed Foundry release version. 2. Download the corresponding release artifact from the official release channel to a local file. 3. Obtain the expected checksum or signature through an authenticated, documented channel. 4. Verify the artifact cryptographically before extracting or executing it. 5. Abort installation if verification fails. 6. Install only into a user-controlled directory and avoid elevated privileges unless they are demonstrably necessary. 7. Present the resolved URL, version, and verification result to the user before execution. 8. Periodically review and deliberately update the pinned version rather than automatically consuming mutable installer content. If the official installation script must be offered as an alternative, download it to a file first, clearly warn that it executes third-party code, and require explicit user review and approval before running it. Merely separating `curl` and `bash` without integrity verification does not fully resolve the supply-chain risk. ]]>