T03 · Remote Payload Retrieval and Execution
- Location
skill.md:17- Finding
Unverified Remote Script Executed Directly by Shell
- Content
View full analysis
Vulnerability Details
File Location:
skill.md, line 17
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: CriticalComplete Code Snippet:
bash curl -fsSL https://jimeng.jianying.com/cli | bashTechnical Analysis
The installation instruction downloads a mutable script from an external URL and pipes it directly into
bash. The script is executed without being saved for inspection, pinned to a specific version, or verified through a cryptographic signature or published checksum.HTTPS provides transport protection but does not guarantee that the endpoint, its hosting infrastructure, or the script itself will remain trustworthy. Although the document describes this as the official installation method, the audited project contains no independent integrity information that would allow the retrieved payload to be verified. The effective code can also change after the Skill has been reviewed.
Direct arbitrary shell execution exceeds the minimum privileges needed for the Skill's declared function of operating an image and video generation CLI. The downloaded script inherits the privileges and environment of the user or Agent that executes the instruction.
Attack Path
- An Agent or user follows the installation instruction in
skill.md. curlretrieves the current response from the external endpoint.- The response is streamed directly to
bashwithout inspection or integrity verification. - If the endpoint, distribution infrastructure, DNS resolution, trusted delivery account, or hosted script is compromised, attacker-controlled shell commands execute immediately.
- Those commands inherit the invoking process's user permissions and can access resources available to that account.
Impact Assessment
A malicious remote payload could read or modify files accessible to the invoking user, access environment variables and locally available credentials, alt ...[truncated 471 chars]
- An Agent or user follows the installation instruction in
- Remediation
View remediation
Remediation Suggestions
- Replace the
curl | bashpipeline with a version-pinned package or release artifact obtained from a documented official distribution channel. - Download the artifact to a local file without executing it automatically.
- Verify a publisher-provided cryptographic signature or a SHA-256 checksum obtained through a separately trusted channel.
- Allow the user or Agent to inspect the downloaded installer before execution.
- Require explicit user consent before installation and clearly document the files, directories, network access, and configuration changes the installer performs.
- Run installation with ordinary user privileges wherever possible and do not invoke or request
sudoimplicitly. - Prefer a package manager that supports version locking, provenance metadata, signature validation, and reproducible updates.
- If a shell installer must be retained, pin an immutable, versioned URL and publish both its expected digest and a safe staged installation procedure.
- Replace the
