T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:200
- Finding
- Python Dependency Installation Without Integrity Verification<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:200` **Vulnerability Type**: Unverified third-party Python dependency installation **Risk Level**: Medium ### Complete Code Snippet ```bash pip install scavio==0.15.0 ``` ### Technical Analysis The Skill instructs users or agents to install the `scavio` package from pip’s configured package index. Although the package version is pinned, the instruction provides no cryptographic hash, lockfile, verified package provenance, or trusted index configuration. Version pinning improves reproducibility but does not verify package integrity. Python package installation can invoke build backends or other installation-time code. The package may also introduce transitive dependencies that are not explicitly pinned or integrity-checked. No evidence establishes that `scavio==0.15.0` is currently malicious. The risk arises from trusting a remotely distributed executable dependency without integrity controls. ### Attack Path 1. An attacker compromises the package publisher, distribution account, registry infrastructure, or a transitive dependency. 2. Malicious code is introduced into the referenced package artifact or one of its dependencies. 3. A user or agent follows the Skill documentation and runs `pip install scavio==0.15.0`. 4. Installation or build-time code executes with the privileges of the installing process. 5. The malicious component reads accessible environment variables, files, or credentials, potentially including `SCAVIO_API_KEY`, and may perform additional actions permitted by the current user. ### Impact Assessment Successful exploitation could execute arbitrary code with the privileges of the account performing the installation. The accessible scope may include: - Environment variables, including `SCAVIO_API_KEY` - Files readable or writable by the current user - Network access available to the installation process - Python environments and project files writable by that account - Ad ...[truncated 251 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions - Publish and verify cryptographic hashes for the exact package artifacts. - Provide a hash-locked requirements file and recommend installation with hash enforcement, for example: ```bash pip install --require-hashes -r requirements.txt ``` - Pin and audit transitive dependencies using a reviewed lockfile. - Specify an approved package index rather than relying implicitly on arbitrary local pip configuration. - Verify package publisher identity and release provenance. - Recommend installation inside an isolated virtual environment or container under a non-privileged account. - Keep API keys and unrelated secrets out of the installation process environment where practical. - State that the SDK is optional because the documented HTTPS API can be called directly without installing it. ]]>