T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:42- Finding
Unpinned Remote Payload Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 42-45
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Mediumbash git clone https://github.com/openclaw-skills/ai-intelligent-3d-model-generation cd ai-intelligent-3d-model-generation pip install -r requirements.txt python app.pyTechnical Analysis
The installation instructions clone a remote Git repository without specifying a reviewed commit hash or signed release. They subsequently install dependencies from the remotely retrieved
requirements.txtand execute the retrievedapp.py.Neither the dependency manifest nor the application is included in the audited artifact. The effective executable payload can therefore change after this Skill has been reviewed. If the upstream repository, maintainer account, or referenced dependency supply chain is compromised, the documented workflow can install and run attacker-controlled code.
Attack Path
- An attacker compromises the upstream repository, a maintainer account, or a package referenced by its dependency manifest.
- The attacker modifies
app.py,requirements.txt, or an installable dependency to contain a malicious payload. - A user follows the instructions and clones the repository's current state without verifying a commit, signature, or checksum.
pip install -r requirements.txtruns package installation logic from the unverified dependency set.python app.pydirectly executes the unverified remote application.- The malicious payload operates with the privileges and data access of the user running these commands.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the invoking user's account. The resulting scope may include reading or modifying files accessible to that account, accessing environment variables and locally available credentials, making network requests, and altering the user's development environment. Elevated system-wide ...[truncated 152 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the reviewed implementation and dependency lock file directly in the Skill package so that the audited content matches the executed content.
- If remote retrieval is necessary, pin the repository to a specific reviewed commit hash rather than cloning the mutable default branch.
- Verify a trusted release signature or published checksum before installing or executing downloaded content.
- Pin every Python dependency and transitive dependency to an exact reviewed version.
- Require cryptographic hashes for Python packages, such as through a hash-locked requirements file and
pip install --require-hashes. - Disable unnecessary package installation scripts where feasible and obtain packages only from explicitly trusted indexes.
- Run installation and execution in an isolated, least-privilege virtual environment or container without unnecessary credentials, sensitive mounts, or host access.
- Establish a controlled update process in which repository revisions and dependency changes are reviewed before updating the pinned references.
