T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Mutable and Unverified Python Dependencies
- Content
View full analysis
=20230314 vosk>=0.3.45 pytest>=7.0.0 ``` Associated installation configuration: ```yaml install: - id: python-deps kind: python requirements: "requirements.txt" - id: ffmpeg kind: apt packages: ["ffmpeg"] ``` ### Technical Analysis All Python dependencies use open-ended minimum-version constraints. The installer can therefore resolve and install future package versions that were not present during the audit. No lock file, exact transitive dependency versions, artifact hashes, or trusted-index restrictions are supplied. Python package installation can execute package build or installation logic. Consequently, compromise of an allowed future package release, one of its transitive dependencies, or the configured package repository could result in attacker-controlled code executing during installation or subsequent import. The test framework `pytest` is included in the primary requirements file even though it is only needed for development and testing. This unnecessarily expands the production dependency graph and supply-chain attack surface. ### Attack Path 1. An attacker compromises a permitted future release of a listed package, one of its transitive dependencies, or the package source used by the installer. 2. The Skill is installed or its dependencies are upgraded after the compromised version becomes eligible under the `>=` constraints. 3. The package resolver selects and downloads the compromised artifact because no exact version or hash prevents it. 4. Attacker-controlled installation, build, or imported runtime code executes. 5. The payload gains the same local permissions and environmental access as the user or service performing installation or running the Sk ...[truncated 595 chars]- Remediation
View remediation
