T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:29- Finding
Unpinned Remote Code and Dependency Retrieval
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29-37
Vulnerability Type: Remote payload retrieval and insecure dependency installation
Risk Level: Mediumbash git clone https://github.com/BENZEMA216/tradingcoach.git ~/tradingcoach cd ~/tradingcoach python3 -m venv .venv && source .venv/bin/activate pip install -r requirements.txt && cp config_template.py config.py # 一键复盘 python scripts/import_trades.py /path/to/trades.csv # 导入 python scripts/run_matching.py # 配对 python scripts/score_positions.py --all # 评分 python scripts/analyze_scores.py # 报告Technical Analysis
The documented installation process clones the current state of an external GitHub repository without pinning a reviewed commit, verifying a cryptographic checksum, or requiring a signed release. It then installs dependencies from a remotely obtained
requirements.txtand executes scripts that are absent from the audited artifact.Because the effective implementation can change after this skill package has been reviewed, the security properties of the invoked scripts cannot be established from the artifact. The dependency installation is also not reproducible or integrity-protected: no lockfile, exact versions, or package hashes are supplied.
A Python virtual environment isolates package placement but does not sandbox execution. Installation hooks and downloaded scripts retain the invoking user's normal filesystem, process, and network privileges.
Attack Path
- An attacker compromises the referenced GitHub account or repository, gains control of a dependency source, or otherwise causes malicious content to appear in the repository or its dependency definitions.
- A user follows the instructions and clones the mutable default branch.
- The user executes
pip install -r requirements.txt; malicious package installation hooks could run at th ...[truncated 925 chars]
- Remediation
View remediation
Remediation Suggestions
- Bundle the reviewed implementation with the skill so its executable behavior is included in the audit scope.
- If remote retrieval remains necessary, pin the repository to a specific reviewed commit rather than cloning a mutable default branch.
- Distribute signed releases and verify signatures or cryptographic checksums before installation or execution.
- Use a dependency lockfile containing exact versions and hashes. Install with an integrity-enforcing command such as
pip install --require-hashes -r requirements.txt. - Review direct and transitive dependencies and use trusted package indexes explicitly.
- Disable unnecessary network access while processing brokerage records and restrict filesystem access to the required input and output directories.
- Document what financial data is read, retained, logged, or transmitted.
- Run the processing scripts under a dedicated, least-privileged account or an appropriately isolated environment.