T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:25- Finding
Unverified Remote Installer Executed Through a Shell Pipeline
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:21-26; the same unsafe command is repeated as an installation requirement inscripts/burn_subtitles.py:24-28
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalComplete Code Snippet:
bash # macOS brew install ffmpeg yt-dlp # uv (Python environment management, automatically handles dependencies) curl -LsSf https://astral.sh/uv/install.sh | shThe renderer documentation repeats the command:
python Requirements: - ffmpeg/ffprobe installed (brew install ffmpeg) - uv installed (curl -LsSf https://astral.sh/uv/install.sh | sh) - macOS font: /System/Library/Fonts/STHeiti Medium.ttcTechnical Analysis
The installation instructions retrieve shell code from a mutable external URL and immediately execute it using
sh. The downloaded content is not pinned to a reviewed release and is not verified using a cryptographic hash or signature. HTTPS protects the connection in transit, but it does not ensure that the server, DNS resolution, certificate trust chain, or remotely hosted installer remains uncompromised.Because the response is never saved for inspection, users cannot verify which commands will execute. The effective payload may also change after the Skill package has been audited. Installing
uvis ancillary environment setup and does not require piping unverified network content directly into a shell, so this behavior exceeds the minimum execution exposure necessary for subtitle processing.Attack Path
- A user follows the setup instructions and runs the documented command.
curlconnects tohttps://astral.sh/uv/install.shand retrieves the installer content available at that moment.- A compromise of the distribution server, DNS or certificate trust path, or published installer causes attacker-controlled shell commands to be returned.
- The pipe passes that content di ...[truncated 903 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all
curl | shinstallation instructions, including the copy in the renderer's documentation. - Prefer a trusted operating-system package manager with a version-pinned package:
bash brew install uv - If direct artifact installation is necessary, pin an exact release rather than using a mutable installer endpoint.
- Download the release artifact to disk, verify its publisher-provided cryptographic signature or SHA-256 checksum, and only then install it.
- Document the expected artifact version, source URL, checksum, and verification commands.
- Run installation without administrator privileges unless the selected installation method strictly requires elevation.
- Keep installation separate from Skill execution so users can review and approve environment changes before processing any media.
- Remove all
