T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:22- Finding
Remote Installation Script Is Executed Without Integrity Verification
- Content
View full analysis
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` for installation instructions. ``` ### Technical Analysis The downloaded response is piped directly into Bash without first saving and inspecting the script, pinning a version, or verifying a cryptographic checksum or signature. Although HTTPS protects the connection in transit, it does not protect against a compromised origin, CDN, publishing account, or upstream script that changes after this Skill has been reviewed. Direct execution is not necessary for the declared ECS patch-management functionality. Installing the CLI is an ancillary setup operation and can be performed using a version-pinned, integrity-verified package. ### Attack Path 1. An attacker compromises the script origin, CDN distribution path, DNS resolution, TLS endpoint, or upstream publishing account. 2. The attacker replaces `setup.sh` with a malicious shell payload. 3. A user or Agent follows the mandatory-looking installation instruction. 4. `curl` retrieves the current attacker-controlled response. 5. Bash executes the response immediately, without any opportunity for integrity validation or review. 6. The payload acts with the privileges and environment of the invoking user. ### Impact Assessment Successful exploitation permits arbitrary local command execution. Depending on the invoking account, the payload could: - Read or modify files accessible to the user. - Access Aliyun CLI profiles and other local credentials. - Modify shell configuration or install persistent components. - Alter binaries or configuration used in later cloud operations. - Use the user's authenti ...[truncated 266 chars]- Remediation
View remediation
