T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:9
- Finding
- Unpinned Third-Party CLI Installation Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md`, lines 9-18 **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```markdown ## Prerequisites This skill requires **hologres-cli** to be installed first: ```bash pip install hologres-cli export HOLOGRES_SKILL=hologres-slow-query-analysis ``` All SQL execution and GUC parameter operations depend on `hologres-cli` commands (`hologres sql run`, `hologres guc set`). ``` ### Technical Analysis The skill directs users or agents to install `hologres-cli` without specifying an exact version, package hash, or trusted package index. Consequently, the installed artifact is determined at execution time rather than audit time. If a future release of the package is compromised, its publisher account is taken over, or package resolution is redirected to an attacker-controlled repository, installation may execute attacker-controlled package build or installation logic. The risk is increased because all subsequent SQL and configuration operations are delegated to this CLI, making the installed package part of the skill's trusted execution path. No malicious dependency payload is included in the audited project itself. The vulnerability is the unsafe, mutable dependency installation procedure. ### Attack Path 1. An attacker compromises the upstream `hologres-cli` distribution channel, publisher account, or package source used by the victim's Python configuration. 2. The attacker publishes a malicious version under the expected package name. 3. A user or agent follows the documented `pip install hologres-cli` command. 4. `pip` resolves and installs the attacker-controlled release because no version or integrity constraint is present. 5. Malicious installation hooks or CLI runtime code execute with the privileges of the account performing the installation. 6. Later `hologres` commands may capture database creden ...[truncated 663 chars]
- Remediation
- ## Remediation Suggestions 1. Pin `hologres-cli` to a reviewed exact version, for example: ```bash python -m pip install 'hologres-cli==REVIEWED_VERSION' ``` 2. Use a locked requirements file containing cryptographic hashes and install with hash verification: ```bash python -m pip install --require-hashes -r requirements.txt ``` 3. Explicitly configure an approved package index rather than relying on ambient `pip` configuration. 4. Verify package provenance, signatures, publisher ownership, and release hashes before updating the pinned version. 5. Install the CLI in an isolated virtual environment with minimum operating-system privileges. 6. Review each dependency update before changing the lock file, and run dependency and malware scans on the resolved artifacts. 7. Avoid executing package installation automatically when the skill is loaded; require explicit user approval.