T08 · Insecure Dependencies
Note
- Location
requirements.txt:1- Finding
Unpinned Third-Party Dependency Permits Supply-Chain Drift
- Content
View full analysis
=2.20.0 ``` `README.md:47-49`: ```bash pip install -r requirements.txt ``` `SKILL.md:27-28`: ```bash pip install requests ``` ### Technical Analysis The dependency specification accepts any `requests` release newer than or equal to version 2.20.0. No lock file or cryptographic package hashes are provided. The direct installation command in `SKILL.md` is even less restrictive. Consequently, installations are not reproducible and depend on the package index, resolver state, and available package versions at installation time. A compromised package repository, maliciously configured index, compromised eligible release, or future incompatible release could introduce unintended code into the Skill's environment. This is a supply-chain hardening weakness rather than evidence that the current `requests` package is malicious. ### Attack Path 1. A user follows the documented installation instructions. 2. `pip` contacts the configured package index or mirror. 3. The resolver selects any eligible version because the dependency is not pinned. 4. If the index, mirror, eligible artifact, or dependency chain has been compromised, the malicious package is downloaded and installed. 5. Package installation or imported runtime code executes with the privileges of the user running `pip` or the Skill. 6. When the Skill subsequently runs, compromised dependency code could access the HeartVoice API token, ECG payloads, API responses, and other resources available to that process. Successful exploitation requires compromise or malicious control of a configured package source or eligible dependency artifact; the repository itself does not contain such a payload. ### Impact Assessment M ...[truncated 527 chars]- Remediation
View remediation
``` 2. Pin all transitive dependencies using a lock-generation tool such as `pip-tools`. 3. Generate and verify cryptographic hashes: ```bash pip-compile --generate-hashes requirements.in pip install --require-hashes -r requirements.txt ``` 4. Replace the unrestricted command in `SKILL.md` with installation from the reviewed, hash-locked requirements file. 5. Document that dependencies must be downloaded from the official PyPI index or an approved internal mirror. 6. Use automated dependency scanning and periodically update pinned versions after security review. 7. Install and run the Skill as a non-privileged user in an isolated virtual environment or container to limit the impact of a compromised dependency. ]]>