T08 · Insecure Dependencies
- Location
SKILL.md:370- Finding
Unpinned Third-Party Dependencies Create a Supply-Chain Execution Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:370-378
Vulnerability Type: Unpinned runtime dependencies
Risk Level: MediumVulnerable Code
bash pip install PyMuPDF pip install pdfplumber pip install python-docx pip install pandas openpyxlTechnical Analysis
The installation instructions do not pin package versions, verify package hashes, use a reviewed lockfile, or require an isolated environment. Consequently, the exact code installed and executed can change after the Skill has been reviewed.
Python package installation may execute package-controlled build or installation logic. If a dependency release or its distribution channel is compromised, following these instructions could execute attacker-controlled code. The finding does not establish that any listed package is currently malicious; it identifies an unsafe dependency-management practice that exposes users to future upstream or supply-chain compromise.
Attack Path
- An attacker compromises an upstream package account, distribution artifact, or dependency release.
- A user follows the Skill instructions at a later date.
pipresolves the mutable package name to the compromised release.- Package-controlled installation logic executes under the user's account.
- The installed package can execute again when the resume-processing workflow imports it.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running
pipor the resume processor. Accessible data may include candidate resumes, generated reports, files available to the user, environment variables, and application credentials. If combined with the separate recommendation to run as administrator, the potential scope could expand to system-level modification.- Remediation
View remediation
Remediation Suggestions
- Pin every direct and transitive dependency to a reviewed version.
- Publish a lockfile or requirements file containing cryptographic hashes.
- Install with hash verification, such as
pip install --require-hashes -r requirements.txt. - Install dependencies in a dedicated, least-privileged virtual environment.
- Use an approved package index and disable unexpected fallback indexes.
- Perform dependency vulnerability and provenance scanning before releases.
- Document a controlled update process rather than resolving the newest package versions at installation time.
