T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:14
- Finding
- Unpinned Third-Party Package Installation<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, line 14 **Vulnerability Type**: Unpinned dependency installation from a third-party package index **Risk Level**: Medium ### Vulnerable Code ```markdown - `docling` CLI must be installed (e.g., via `pipx install docling`) ``` ### Technical Analysis The suggested installation command does not specify an exact Docling version, constrain transitive dependencies, or verify package integrity through hashes or signatures. It therefore installs whichever release and dependency graph the configured package index resolves at installation time. This creates a supply-chain risk: the code installed by users can differ from the code considered during this audit. A compromised maintainer account, malicious future release, dependency confusion event, or compromised transitive dependency could result in attacker-controlled package installation or build logic being executed locally. The project metadata declares version `1.0.2`, but this does not constrain the version installed by `pipx install docling`. ### Attack Path 1. An attacker compromises the Docling package, one of its transitive dependencies, a maintainer account, or the package distribution channel. 2. The attacker publishes a malicious release that satisfies the unconstrained installation request. 3. A user follows the documented prerequisite and runs `pipx install docling`. 4. The package manager downloads the attacker-controlled release and executes applicable build or installation logic. 5. The malicious package subsequently runs with the privileges of the installing user whenever the CLI is invoked. ### Impact Assessment Successful exploitation could execute arbitrary code under the account performing the installation. That code could access files, credentials, environment variables, and network resources available to that user. The scope depends on the installation environment and becomes more severe if package installation is performed ...[truncated 145 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions - Pin Docling to a specifically reviewed version, for example `pipx install 'docling==<reviewed-version>'`. - Use a lock file or equivalent mechanism to constrain transitive dependency versions. - Verify package artifacts using cryptographic hashes or trusted signatures. - Explicitly configure a trusted package index and disable unintended fallback indexes. - Periodically review pinned dependencies for known vulnerabilities before updating them. - Perform installation and document processing as an unprivileged user in an isolated environment. ]]>