T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:31- Finding
Unverified Remote Installer Executed Directly by a Shell
- 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 installation command sends mutable network content directly to `bash`. It does not pin an installer version, verify a cryptographic checksum or signature, save the script for inspection, or constrain the installer in a sandbox. The hostname appears related to Alibaba Cloud, but reliance on a recognizable hostname is not an adequate integrity control. The effective code executed by the Skill can change after the Skill package has been audited. Compromise of the hosting infrastructure, its deployment process, DNS resolution, or the TLS trust path could therefore turn this instruction into arbitrary code execution. Installing the Aliyun CLI is only necessary for the optional OpenAPI configuration checks. Basic DNS and WHOIS diagnosis does not require executing a remote installer, so this behavior exceeds the minimum privileges necessary for the Skill's core functionality. ### Attack Path 1. An attacker compromises or alters the remotely hosted `setup.sh`, or compromises a relevant network trust component. 2. A user invokes the Skill on a machine where the required Aliyun CLI version is absent. 3. The agent follows the documented installation command. 4. `curl` retrieves the current attacker-controlled response. 5. The response is immediately interpreted by `bash` without any integrity verification. 6. The payload executes with all privileges available to the agent or user and can access their files, credentials, and network resources. ### Impact Assessment Successful exploitation provides arbitrary co ...[truncated 354 chars]- Remediation
View remediation
