T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:69
- Finding
- Unverified Remote Foundry Installer Executed Directly by Shell## Vulnerability Details **File Location**: `SKILL.md:69` **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High **Vulnerable Code Snippet**: ```markdown - Foundry installed: `curl -L https://foundry.paradigm.xyz | bash && foundryup` ``` ### Technical Analysis The installation command downloads mutable content from an external URL and passes it directly to Bash. The response is not pinned to a specific release and is not subjected to checksum validation, signature verification, inspection, or an integrity check before execution. Installing Foundry is relevant to the Skill's stated purpose, but direct remote-to-shell execution exceeds the minimum privilege and trust necessary to install it. The effective code can change after the Skill has been reviewed. Compromise of the upstream service, its deployment pipeline, DNS resolution, TLS termination, or another delivery component could therefore turn this instruction into arbitrary code execution. The subsequent `foundryup` command also retrieves and installs executable tooling according to upstream state rather than a version and artifact whose integrity has been independently verified. ### Attack Path 1. An attacker compromises the remote installer endpoint or an element of its delivery chain. 2. The attacker modifies the installer response to include malicious shell commands. 3. A user or agent follows the prerequisite and executes the documented command. 4. `curl` retrieves the attacker's current response. 5. Bash executes the response immediately without an opportunity for integrity validation or review. 6. The payload accesses or modifies resources available to the invoking account, potentially including project files, shell configuration, credentials, and blockchain wallet keys. 7. Because `foundryup` is chained with `&&`, additional mutable executable components may be retrieved after the initial script succeeds. ### ...[truncated 652 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the direct `curl | bash` pipeline. 2. Link users to official installation documentation rather than automatically executing remotely supplied code. 3. Prefer a version-pinned binary or source archive from the official Foundry release repository. 4. Download the selected artifact to a local file before execution. 5. Verify its cryptographic checksum and, where available, its publisher signature against values obtained through a trusted channel. 6. Require explicit user inspection or approval before running any installer. 7. Pin the installed Foundry version instead of allowing `foundryup` to select mutable upstream state. 8. Perform installation from an unprivileged account or isolated environment, and do not expose wallet keys or API credentials during installation. 9. Document the expected installer hash, release version, and trusted source so users can reproduce the integrity check.