T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:100- Finding
Unverified Remote Installation Script Is Piped Directly into Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:100-103
Vulnerability Type: Remote payload retrieval and immediate shell execution
Risk Level: CriticalVulnerable Code:
markdown > 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 update, > or see [references/cli-installation-guide.md](references/cli-installation-guide.md) for installation instructions.Technical Analysis
The installation instruction downloads a mutable shell script from an external URL and passes the response directly to Bash. The content is neither pinned to a reviewed release nor checked against a cryptographic signature or known digest before execution.
HTTPS provides transport authentication but does not establish payload immutability. If the hosting origin, CDN, DNS resolution, TLS trust chain, or upstream deployment process is compromised, the downloaded content can be replaced after the Skill has been reviewed. Piping the response directly into Bash also prevents meaningful inspection before execution.
This behavior is not necessary for the declared backup functionality. The included installation guide already documents package-manager and version-specific binary installation alternatives that avoid immediate execution of an arbitrary remote script.
Attack Path
- The Skill determines that Aliyun CLI is absent or older than version 3.3.3.
- The Agent invokes the documented
curl | bashcommand. - An attacker with control over, or the ability to compromise, the remote delivery path supplies a modified
setup.sh. - Bash executes the response immediately with the privileges of the Agent or invoking user.
- The malicious script can access local files and credentials, modify executable files, or tamper with subsequent authenticated cloud operations.
Impact Assessment
Successful exploitation pro ...[truncated 734 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashinstallation path. - Pin installation to a specific reviewed CLI version rather than retrieving a mutable installer.
- Download the artifact to a local file without executing it.
- Verify a vendor-published cryptographic signature or SHA-256 digest obtained through an independently authenticated channel.
- Inspect and extract the verified archive before placing the executable in
PATH. - Prefer a trusted operating-system package manager where available.
- Require explicit user approval before installing or replacing local software.
- Run installation with ordinary user privileges whenever possible and request elevation only for the narrowly scoped file operation that requires it.
- Remove the direct
