T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:24- Finding
Unverified Remote Installation Script Executed Directly by Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 24-26
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
text > 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 streams a mutable response from an external URL directly into
bash. The payload is not pinned to an immutable release, saved for inspection, or verified using a cryptographic signature or trusted checksum.Although the URL appears to be an Alibaba Cloud distribution domain, domain ownership alone does not guarantee that every future response will be safe. Compromise of the origin, CDN, DNS path, TLS termination infrastructure, or release process could change the effective code after this Skill has been reviewed.
Executing a network response directly also prevents users from meaningfully reviewing the installer before execution. This behavior is unnecessary for the Skill's resource inventory functionality because package-manager installation or a verified, versioned binary can provide the required CLI without creating a direct remote code-execution channel.
Attack Path
- An attacker compromises the installation origin, CDN, DNS resolution path, or upstream release process.
- The attacker modifies
setup.shto contain malicious shell commands. - A user or agent follows the prerequisite instructions because Aliyun CLI is absent or outdated.
curlretrieves the attacker-controlled response and immediately passes it tobash.- The payload executes with the privileges of the user running the Skill.
- The payload can inspect local files and environment variables, alter executables or configuration, establish persistence where permitted ...[truncated 643 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashinstallation path. - Prefer a trusted operating-system package manager with a version constraint.
- If direct binary installation is required:
- Pin an explicit CLI version rather than using a mutable “latest” artifact.
- Download the archive to a local file.
- Retrieve the expected checksum or signature through a separately authenticated channel.
- Verify the artifact before extraction or execution.
- Present the source and verification result to the user before installation.
- Do not perform installation automatically from an agent session; request explicit user approval.
- Run installation with ordinary user privileges wherever possible and avoid unnecessary
sudoexecution. - Document the expected publisher, version, checksum algorithm, and signature-verification procedure.
- Remove the
