T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:43- Finding
Unverified Remote Script Is Downloaded and Executed by a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:43
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: CriticalVulnerable Code
bash curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bashTechnical Analysis
The installation instruction pipes content retrieved from an external URL directly into
bash. The script is not pinned to a reviewed version, saved for inspection, or validated using a cryptographic checksum or signature.HTTPS authenticates the connection under the normal certificate-authority model, but it does not establish that the mutable script still contains the same code that was present when the Skill was audited. Compromise of the hosting service, CDN, publishing account, DNS/TLS trust path, or upstream release process could change the effective payload without modifying this repository.
This behavior is not required for the Skill's core read-only DataWorks queries. Installation can be handled through a verified package or a separately reviewed, version-pinned artifact.
Attack Path
- An attacker compromises the hosted script, its publishing process, or another part of its delivery chain.
- A user or Agent follows the mandatory prerequisite in
SKILL.md. curlretrieves the attacker's current script content.- The pipe passes that content directly to
bashwithout an inspection or integrity-verification boundary. - The script executes arbitrary commands with the privileges of the user running the Agent.
- The payload could read accessible files and cloud credential configuration, alter local tools, download additional payloads, or establish persistence.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking account. The affected scope includes all files and processes accessible to that account, the Agent workspace, Aliyun CLI configuration, and cloud credentials available to loca ...[truncated 358 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashinstruction entirely. - Prefer an authenticated official package repository whose package metadata and signatures are verified by the package manager.
- If direct installation is unavoidable:
- Pin an exact release version and platform artifact.
- Download the artifact to a local file rather than piping it into a shell.
- Obtain the expected digest through a separately authenticated vendor channel.
- Verify a strong checksum such as SHA-256 and, preferably, a vendor signature.
- Abort installation on any verification failure.
- Allow the user to inspect the installer before execution.
- Do not run the installer with elevated privileges unless installation genuinely requires it and the user explicitly approves the elevation.
- Document the expected filename, version, digest, signing identity, and destination path.
- Remove the
