T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:5- Finding
Unverified Remote Installer Execution on Unix and Windows
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:5andSKILL.md:64-66
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: HighVulnerable Code
text "install":"curl -fsSL https://asale.ai/dl/install.sh | sh", "installAlternative":"irm https://asale.ai/dl/install.ps1 | iex"sh curl -fsSL https://asale.ai/dl/install.sh | sh irm https://asale.ai/dl/install.ps1 | iexThe documentation also states that
asale updatereruns the same installer.Technical Analysis
The Unix command pipes an HTTPS response directly into
sh, while the Windows alternative passes a remotely retrieved PowerShell response directly toInvoke-Expression. In both cases, the downloaded content executes before the user can inspect it.The installation process does not pin an installer version, validate a cryptographic digest, verify a release signature, or establish that the response matches the linked source repository. HTTPS protects the connection in transit but does not prevent a compromised domain, web server, deployment pipeline, or signing infrastructure from serving a changed payload after this Skill has been reviewed.
A companion daemon may be necessary for the declared switching functionality, but executing a mutable and unverified network response is not the minimum capability required to install it. A versioned and authenticated package would provide the required functionality with lower supply-chain risk.
Attack Path
- An attacker compromises
asale.ai, its deployment pipeline, or another component capable of controlling the installer response. - The attacker replaces
install.shorinstall.ps1with a malicious payload. - A user or agent follows the Skill's installation or update instructions.
curlor PowerShell retrieves the attacker-controlled response.shorInvoke-Expressionimmediately executes the response without integrity or signa ...[truncated 756 chars]
- An attacker compromises
- Remediation
View remediation
Remediation Suggestions
- Replace the shell pipelines with downloads of versioned release artifacts.
- Pin an explicit installer or package version rather than using a mutable endpoint.
- Publish a cryptographic digest through an independently authenticated release channel and verify it before execution.
- Prefer signed platform packages and enforce signature verification.
- Download scripts to disk and require inspection or explicit confirmation before execution.
- Ensure
asale updateapplies the same version-pinning and verification controls. - Document the files, services, permissions, persistence mechanisms, and network endpoints introduced by installation.
- Do not request administrator or root privileges unless a documented installation operation strictly requires them.
