T08 · Insecure Dependencies
- Location
SKILL.md:481- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 481–483
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash pip install pdfplumberThe installed dependency is subsequently imported and used at lines 60 and 151:
python import pdfplumberpython with pdfplumber.open(pdf_path) as pdf:Technical Analysis
The setup instructions install
pdfplumberwithout a fixed version or integrity hash. Consequently, installation resolves whichever compatible release and transitive dependencies are available from the configured Python package index at execution time. The reviewed Skill also declares theexectool, enabling an Agent to run this installation command.This creates a mutable software supply-chain boundary: future upstream changes, a compromised package index or publisher account, or dependency-resolution behavior involving an unsafe configured index could introduce unreviewed code. Python package installation can execute build backends and other installation-time components, while the resulting package executes during drawing analysis.
The audit found no evidence that
pdfplumberis currently malicious, no typosquatted package name, and no intentionally unsafe package source. The risk arises from missing version and integrity controls rather than a confirmed malicious payload.Attack Path
- A user or Agent follows the Skill's setup instructions.
- The declared
execcapability runspip install pdfplumber. - Package resolution retrieves an unpinned release and its transitive dependencies from the environment's configured package index.
- If an upstream artifact, publisher account, index, or dependency-resolution source has been compromised, attacker-controlled package code may run during installation or later import.
- The installed dependency is imported and processes user-supplied drawing files under the Agent's operating-system identit ...[truncated 570 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
pdfplumberand every transitive dependency to versions that have been reviewed and tested. - Maintain dependencies in a lock file generated through a reproducible dependency-management workflow.
- Require package hashes, such as with
pip install --require-hashes -r requirements.txt, to verify artifact integrity. - Install only from an explicitly trusted package index and disable unintended supplemental indexes.
- Perform installation in a dedicated, non-privileged virtual environment or isolated container.
- Scan locked dependencies for known vulnerabilities and review updates before changing pins.
- Separate setup from normal Skill execution and remove or restrict the
execcapability after dependencies are provisioned. - Process untrusted PDFs in a sandbox with restricted filesystem and network access to limit the effect of parser or dependency compromise.
- Pin
