T08 · Insecure Dependencies
Warning
- Location
- package.json:11
- Finding
- Unpinned pywin32 Dependency Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `package.json:11`, `README.md:7-9`, `SKILL.md:59-62` **Vulnerability Type**: Unpinned third-party dependency **Risk Level**: Medium ### Vulnerable Code `package.json:11`: ```json "requirements": ["pywin32"], ``` The corresponding installation command in `README.md:7-9` and `SKILL.md:59-62` is: ```bash pip install pywin32 ``` ### Technical Analysis The project instructs users to install `pywin32` without specifying a reviewed version or validating its package integrity. Consequently, installation resolves to whichever release is selected by the package index at installation time. The dependency name is consistent with the project's documented Windows COM functionality, and no suspicious alternative package repository or typosquatted name was found. Nevertheless, the absence of version and hash constraints makes builds non-reproducible and allows upstream package changes to enter the execution environment without project-level review. Python packages and their installation mechanisms can execute code with the permissions of the user performing the installation. Therefore, compromise of the upstream package, release process, package-index account, or dependency delivery channel could result in arbitrary code execution. ### Attack Path 1. An attacker compromises the upstream package distribution process or publishes a malicious release through a compromised maintainer account. 2. A user follows the documented `pip install pywin32` instruction. 3. `pip` resolves and downloads the uncontrolled current release. 4. Malicious package code executes during installation or when `win32com.client` is imported. 5. The payload gains the permissions of the user running the installation or converter. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on those privileges, the attacker could access ...[truncated 320 chars]
- Remediation
- ## Remediation Suggestions 1. Add a dedicated `requirements.txt` containing a reviewed, exact version: ```text pywin32==REVIEWED_VERSION ``` 2. Generate and record a verified SHA-256 hash for the approved distribution: ```text pywin32==REVIEWED_VERSION --hash=sha256:VERIFIED_HASH ``` 3. Require hash validation during installation: ```bash python -m pip install --require-hashes -r requirements.txt ``` 4. Update `README.md` and `SKILL.md` so users install from the locked requirements file rather than resolving the latest release. 5. Review dependency updates before changing the pin and use automated vulnerability and provenance monitoring. 6. Install the dependency in a dedicated virtual environment under a non-administrative account.