T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:22- Finding
Unverified Remote Installation Script Is Executed Directly by Bash
- Content
View full analysis
= 3.3.3 required** > Run `aliyun version` to verify >= 3.3.3. If not installed or version too low, > run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to install/update, > or see [references/cli-installation-guide.md](references/cli-installation-guide.md) for installation instructions. ``` ### Technical Analysis The installation command downloads a mutable shell script and sends it directly to Bash. No version is pinned, and the Skill does not verify a cryptographic signature or checksum before execution. The effective code can therefore change after the Skill package has been reviewed. HTTPS protects the connection to the current endpoint but does not provide artifact reproducibility or protect against compromise of the hosting infrastructure, CDN, DNS path, certificate issuance process, or publisher account. The repository itself contains no copy of `setup.sh`, so its behavior cannot be established through this static audit. Installing a compatible CLI is related to the declared WAF inspection functionality, but direct execution of a mutable remote script is not the least-privileged installation method. A package manager or a separately downloaded, pinned, and cryptographically verified binary would provide the necessary functionality without granting arbitrary remote content immediate shell execution. ### Attack Path 1. An attacker compromises the remote installation endpoint, CDN, DNS route, or publisher account. 2. The attacker replaces `setup.sh` with a malicious shell payload. 3. A user or Agent follows the Skill's pre-check instructions. 4. `curl` retrieves the modified response and streams it directly into Bash. 5. Bash executes the payload without an opportunity for inspection or integrity verification. 6. Th ...[truncated 799 chars]- Remediation
View remediation
