T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:135- Finding
Unpinned Remote Installer Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:135-138
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: Highbash # Clone repository git clone https://github.com/zzlzzlzzl15/Memora.git cd Memora/personal_knowledge_base # Run installation script ./install.shTechnical Analysis
The documented installation process clones the current default branch of a remote Git repository and immediately executes its
install.shscript. The instructions do not pin the repository to a reviewed commit hash or signed release, nor do they require checksum or signature verification.The remotely hosted installer is not included in the audited project. Consequently, its behavior can change after this skill has been reviewed. This creates a time-of-check/time-of-use supply-chain risk: the commands may retrieve and execute code materially different from the code that existed during the audit.
Attack Path
- An attacker compromises the upstream GitHub account, repository, maintainer credentials, or repository publishing workflow.
- The attacker modifies
install.shor another component invoked by that script on the default branch. - A user follows the installation commands in
SKILL.md. git cloneretrieves the attacker-controlled revision because no immutable revision is specified.- The user executes
./install.sh, allowing the modified payload to run locally. - The payload operates with the privileges of the user running the installation and may modify any resources accessible to that account.
Impact Assessment
Successful exploitation permits arbitrary command execution with the invoking user's privileges. Depending on those privileges, the attacker could read or modify user files, steal configured API keys, alter application configuration, install additional software, or compromise knowledge-base data.
If the installation is run with elevated privileges, ...[truncated 198 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the repository checkout to an immutable, reviewed commit hash:
bash git clone https://github.com/zzlzzlzzl15/Memora.git cd Memora git checkout --detach <reviewed-commit-hash> - Prefer a cryptographically signed release and verify the release signature before executing any installer.
- Publish and verify SHA-256 checksums for downloaded release artifacts.
- Include the installer in the auditable skill package when feasible, rather than retrieving executable logic at installation time.
- Review the installer and every script or binary it invokes before execution.
- Run installation with the least-privileged account possible and avoid
sudounless a specific operation requires it. - Add explicit documentation stating that remote code will be executed and identifying the exact reviewed revision.
- Pin the repository checkout to an immutable, reviewed commit hash:
