T03 · Remote Payload Retrieval and Execution
- Location
skill.md:137- Finding
Unverified Remote Executable Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
skill.md, line 137
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighComplete vulnerable instruction, faithfully translated into English:
markdown 1. **First use**: Check whether ClassIslandCLI.exe is in PATH. If it does not exist or is damaged, retrieve the portable package download address from https://gitee.com/api/v5/repos/buger2008/ClassIslandCLI/releases?page=1&per_page=20&direction=desc, download the package for the applicable platform, extract it into PATH.Technical Analysis
The skill directs the agent to obtain an executable from a mutable release endpoint belonging to a third-party repository, extract it into a directory on
PATH, and use it to perform subsequent operations. It does not require an immutable artifact version, expected cryptographic hash, trusted publisher signature, authenticated manifest, or other integrity verification before execution.Consequently, the executable ultimately run by the agent can differ from the payload present when the skill was audited. Compromise of the repository owner account, release infrastructure, API response, or distributed archive could substitute arbitrary executable code. Installing the downloaded program on
PATHalso creates a tool-substitution risk because later calls toClassIslandCLI.exemay resolve to the unverified binary.Attack Path
- An attacker compromises or otherwise gains control over the referenced repository, release account, release artifact, or distribution channel.
- The attacker publishes a modified portable package containing a malicious
ClassIslandCLI.exe. - On first use, or when the existing executable is considered missing or damaged, the agent follows the skill instruction and queries the mutable release endpoint.
- The agent downloads the attacker-controlled package and extracts it into a directory on
PATHwithout validating ...[truncated 863 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove automatic discovery and download of executables from a mutable release endpoint.
- Distribute an audited binary with the skill or use an official, authenticated package-management channel.
- Pin an exact release version and use an immutable artifact URL rather than selecting the latest available release.
- Publish and enforce a known SHA-256 or stronger digest for each supported platform package. Abort installation if verification fails.
- Verify a trusted publisher signature or signed release manifest before extracting or executing the artifact.
- Install the executable in a dedicated, access-controlled application directory rather than a shared
PATHdirectory. - Invoke the verified executable through an absolute path to prevent path-precedence and executable-substitution attacks.
- Extract archives into a controlled temporary directory first, validate archive entries against path traversal, inspect the expected file set, and only then install the verified binary.
- Require explicit user approval before downloading, installing, replacing, or executing an external binary.
- Document the trusted publisher, expected version, hashes, signature-verification procedure, and rollback process in the skill.
