T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:24- Finding
Unverified Remote Installer Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 24–27
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalComplete Code Snippet:
bash # macOS /bin/bash -c "$(curl -fsSL https://dp-public.oss-cn-beijing.aliyuncs.com/bohrctl/1.0.0/install_bohr_mac_curl.sh)" # Linux /bin/bash -c "$(curl -fsSL https://dp-public.oss-cn-beijing.aliyuncs.com/bohrctl/1.0.0/install_bohr_linux_curl.sh)"Technical Analysis
These prerequisite commands retrieve shell scripts from an external object-storage host and pass their contents directly to Bash. The downloaded payload is not present in the audited package, and the commands do not verify a cryptographic signature or pinned checksum before execution. Consequently, the code that ultimately runs can differ from the code reviewed during this audit.
Although installing the Bohrium CLI supports the declared image-management functionality, immediate execution of unverified network content exceeds the minimum privilege and trust necessary to perform that installation. Separating download, integrity verification, inspection, and execution would materially reduce the risk.
Exploitation would require an attacker to control or alter the content delivered by the referenced host, such as through compromise of the storage account or release infrastructure. Compromise of the applicable DNS or TLS trust path could create an equivalent result. The fixed HTTPS destination reduces arbitrary-destination risk but does not establish payload integrity.
Attack Path
- An attacker compromises the external object-storage account, hosted installer, publishing pipeline, or an applicable network trust component.
- The attacker replaces or modifies one of the referenced installer scripts with malicious shell commands.
- A user or agent follows the prerequisite instructions in
SKILL.md. curlretrieves the altered content.- Command substitut ...[truncated 821 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not execute downloaded content through command substitution or a
curl | shellequivalent. - Prefer installation through a trusted package manager whose metadata and artifacts are cryptographically authenticated.
- If a standalone installer is necessary:
- Download it to a non-executable file.
- Pin an immutable artifact version.
- Verify a vendor-published cryptographic signature or an independently distributed SHA-256 checksum.
- Abort on every verification failure.
- Review the downloaded script before execution.
- Execute it with the least-privileged account capable of completing the installation.
- Host an auditable installer in the reviewed project when practical, while separately verifying any binaries it installs.
- Document the files, network destinations, and configuration changes made by the installer.
- Avoid requesting administrator or root privileges unless a specific installation step demonstrably requires them.
A safer documented flow should resemble:
bash curl -fL --proto '=https' --tlsv1.2 \ -o install_bohr_linux.sh \ 'https://example.invalid/immutable-version/install_bohr_linux.sh' printf '%s %s\n' 'PINNED_SHA256_VALUE' 'install_bohr_linux.sh' | sha256sum -c - less install_bohr_linux.sh /bin/bash install_bohr_linux.shThe checksum must be obtained through a trusted channel independent of the downloaded artifact.
- Do not execute downloaded content through command substitution or a
