T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- Finding
Mutable Remote Installer Executed Directly by a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:16
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code:
bash curl -fsSL https://cli.inference.sh | sh && infsh loginTechnical Analysis
The command retrieves the current response from
https://cli.inference.shand pipes it directly tosh. The payload is neither pinned to an immutable version nor saved for inspection before execution. No independently trusted signature or hard-coded checksum is validated before the shell interprets the response.Although the documentation states that the installer verifies the downloaded binary's SHA-256 checksum, that does not establish trust in the installer itself. A compromised installer can alter both the downloaded artifact and its verification logic. The effective code can also change after this Skill has been reviewed.
Installing a CLI supports the declared content-generation functionality, but executing a mutable network response directly in a shell exceeds the minimum mechanism necessary. A pinned binary can instead be downloaded and independently verified before execution.
Attack Path
- An attacker compromises the installer host, its deployment credentials, DNS resolution, TLS termination, or another component capable of changing the response from
cli.inference.sh. - The attacker replaces the expected installer with a malicious shell payload.
- A user or Agent follows the Quick Start command in
SKILL.md. curldownloads the attacker-controlled response and passes it directly tosh.- The payload executes immediately with all privileges available to the invoking user.
- The subsequently installed or replaced
infshbinary can also interceptinfsh loginand capture authentication material.
Impact Assessment
Successful exploitation provides arbitrary command execution under the account running the installation comman ...[truncated 437 chars]
- An attacker compromises the installer host, its deployment credentials, DNS resolution, TLS termination, or another component capable of changing the response from
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | shinstallation pattern. - Pin the CLI to an exact reviewed version and immutable artifact URL.
- Download the artifact to a local file without executing it.
- Verify it using a hard-coded SHA-256 digest obtained through a separately trusted channel, or validate a cryptographic signature against a pinned trusted public key.
- Fail closed if verification does not succeed.
- Inspect the downloaded file and its permissions before installation or execution.
- Install the CLI in a user-owned directory without elevated privileges.
- Keep manual installation and verification as the default documented procedure.
- Perform authentication only after verifying that the expected CLI binary is being invoked.
- Remove the
