T08 · Insecure Dependencies
- Location
requirements.txt:4- Finding
Unpinned and Unverified Third-Party Dependencies
- Content
View full analysis
=1.10.0 baostock>=0.8.8 requests>=2.28.0 # Data processing pandas>=1.5.0 numpy>=1.21.0 # Configuration pyyaml>=6.0 # Type hints typing-extensions>=4.0.0 ``` `SKILL.md:30-33`: ```bash pip install -r requirements.txt ``` ### Technical Analysis Every dependency uses an open-ended minimum-version constraint. Consequently, installation may select any newer release available from the configured package index rather than a specific version reviewed with this project. The project does not provide a lock file, package hashes, or an integrity-enforcing installation command. Python package installation can execute package build or installation logic. If an accepted upstream version or the configured package index is compromised, following the documented installation command may introduce and execute attacker-controlled code. Unrestricted upgrades can also introduce unreviewed transitive dependencies. `pyyaml` and `typing-extensions` were not observed in the reviewed runtime imports, so they may unnecessarily expand the dependency and supply-chain attack surface. This finding does not establish that the currently named packages are malicious. The vulnerability is the absence of reproducible version and integrity controls. ### Attack Path 1. An attacker compromises an upstream dependency account, publishing infrastructure, package-index path, or a transitive dependency. 2. The attacker publishes a malicious release whose version satisfies one of the `>=` constraints. 3. A user follows the instruction in `SKILL.md` and runs `pip install -r requirements.txt`. 4. Pip resolves the compromised release because no exact ver ...[truncated 848 chars]- Remediation
View remediation
