T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:27
- Finding
- Unpinned Third-Party Dependency Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 27–31 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium ### Vulnerable Code ```markdown 2. Directly run the following bash command to ensure that the current Python environment has the OpenAI dependency: ```bash pip install 'volcengine-python-sdk[ark]' ``` ``` ### Technical Analysis The Skill instructs the agent to install the latest available release of `volcengine-python-sdk[ark]` directly into the active Python environment. It does not pin an audited version, verify package hashes, use a lockfile, or require an isolated virtual environment. Installing a Python package may execute package-controlled installation logic and introduces transitive dependencies whose versions can change independently. Consequently, the code that runs during future Skill invocations is not fully represented by the audited project. This creates a supply-chain risk if the named package, one of its dependencies, or the configured package index is compromised. This finding does not establish that the named package is malicious. The vulnerability is the uncontrolled and non-reproducible dependency installation procedure. ### Attack Path 1. An attacker compromises a future release of the dependency, one of its transitive dependencies, or the package-index delivery path. 2. The agent follows `SKILL.md` and executes the unpinned `pip install` command. 3. The package manager downloads the attacker-controlled release and may execute its installation logic. 4. Malicious code runs with the privileges of the account invoking the Skill. 5. That code could access files and environment variables available to the process, including `ARK_API_KEY`, alter the Python environment, or modify subsequent video-analysis behavior. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the invoking user's privileges. The accessible sc ...[truncated 311 chars]
- Remediation
- ## Remediation Suggestions - Pin the SDK and all transitive dependencies to reviewed versions in a lockfile. - Require package hashes, such as with `pip install --require-hashes -r requirements.txt`. - Install dependencies in a dedicated, non-privileged virtual environment rather than the active global environment. - Use a trusted package index and retain provenance or integrity metadata for approved artifacts. - Periodically scan and deliberately update locked dependencies after security review. - Package the Skill with reproducible environment metadata instead of instructing the agent to install the latest release at runtime.
