T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:26- Finding
Unpinned Remote Payload Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26-34
Vulnerability Type: Remote retrieval and execution of mutable, unaudited code
Risk Level: HighThe installation instructions direct users to clone an externally hosted Git repository from its mutable default branch, copy a downloaded Bash script into their executable path, grant it execute permission, and run it. The externally retrieved script is not included in the audited project, and its integrity is not verified.
markdown **Source:** https://github.com/solomonneas/media-cli **Install:** Clone the repo and copy the script to your PATH. Review it first. ```bash git clone https://github.com/solomonneas/media-cli.git cd media-cli cp media ~/bin/media && chmod +x ~/bin/media media setuptext ### Technical Analysis The `git clone` command retrieves the repository's current default branch without pinning it to an audited commit hash or immutable signed release. No checksum, cryptographic signature, or trusted manifest is used to validate the downloaded `media` script before execution. Consequently, the effective code executed by users can change after this Skill has been reviewed. The instruction to “Review it first” is advisory only and does not provide an enforceable integrity control. Because the downloaded script is absent from the audited artifact, claims that it communicates only with localhost services, does not perform telemetry, and securely handles configuration cannot be independently verified. This behavior most closely matches `T03: Remote Payload Retrieval and Execution`: executable code is obtained from an external URL and immediately prepared and invoked, allowing the effective payload to change independently of the reviewed Skill. ### Attack Path 1. An attacker compromises the upstream repository, a maintainer account, or the repository's mutable default branch. 2. The attacker modifies the upstream `media` ...[truncated 1439 chars]- Remediation
View remediation
Remediation Suggestions
- Vendor the reviewed
mediascript directly in the Skill package so its contents are covered by the same audit and versioning process. - If remote installation remains necessary, pin the source to a specific reviewed commit hash or immutable release artifact rather than the repository's mutable default branch.
- Publish a SHA-256 checksum through a trusted channel and require the installer to verify it before granting execute permission or running the script.
- Prefer cryptographically signed releases and verify the maintainer's signature against a documented trusted public key.
- Make integrity verification fail closed: installation must stop if the checksum or signature is missing or invalid.
- Audit the actual Bash source for command injection, unsafe configuration parsing, insecure temporary files, credential exposure, unexpected outbound requests, and excessive filesystem permissions.
- Avoid placing the executable in
~/binuntil verification has succeeded, and document the exact version or commit expected by the Skill.
- Vendor the reviewed
