T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:78
- Finding
- Unpinned Third-Party Dependencies and Bypassed Environment Protections<![CDATA[ ## Vulnerability Details **File Locations**: - `SKILL.md:78-89` - `SKILL.md:94-105` - `FORMS.md:82-87` **Vulnerability Type**: Unpinned dependencies installed directly from public package registries **Risk Level**: Medium ### Vulnerable Code `SKILL.md:78-89`: ```bash # Python libraries pip install pypdf pdfplumber reportlab pdf2image pytesseract Pillow --break-system-packages # System tools sudo apt-get install -y poppler-utils tesseract-ocr qpdf # For Chinese OCR sudo apt-get install -y tesseract-ocr-chi-sim tesseract-ocr-chi-tra # Node.js (form filling) npm install pdf-lib ``` `SKILL.md:94-105`: ```bash # System tools (required for OCR and CLI operations) brew install qpdf poppler tesseract # IMPORTANT: Language packs must be installed separately for non-English OCR brew install tesseract-lang # Python libraries pip install pypdf pdfplumber reportlab pdf2image pytesseract Pillow --break-system-packages # Node.js (form filling) npm install pdf-lib ``` `FORMS.md:82-87`: ```markdown ### Setup ```bash npm install pdf-lib ``` ``` ### Technical Analysis The installation commands do not pin dependency versions and do not verify package integrity through hashes or lockfiles. Consequently, the exact code installed depends on the package versions returned by the registry at installation time. The Python installation also uses `--break-system-packages`, which bypasses protections intended to prevent package managers from modifying an externally managed Python environment. This can cause dependency replacement or conflicts at the host level rather than containing changes within a project-specific virtual environment. This does not establish that any currently named package is malicious. The security weakness is that installation is non-reproducible and trusts future registry responses without integrity verification. If a dependency release or registry account is compromised, installation-time scripts or imported package code could execute with t ...[truncated 1416 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin every Python and Node.js dependency to a reviewed version. 2. Provide a Python requirements lockfile with cryptographic hashes, for example: ```text pypdf==X.Y.Z --hash=sha256:REVIEWED_HASH pdfplumber==X.Y.Z --hash=sha256:REVIEWED_HASH ``` 3. Install Python dependencies in an isolated virtual environment: ```bash python3 -m venv .venv . .venv/bin/activate python -m pip install --require-hashes -r requirements.txt ``` 4. Remove `--break-system-packages` from the recommended installation process. 5. Commit `package-lock.json` and recommend `npm ci` instead of an unconstrained `npm install`. 6. Use trusted registry configuration and avoid silently falling back to unapproved package indexes. 7. Periodically scan locked dependencies for known vulnerabilities and review updates before changing pinned versions. ]]>