T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:10
- Finding
- Unpinned and Unverified Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 10–14 **Vulnerability Type**: Supply-chain risk from an unpinned third-party dependency **Risk Level**: Medium ### Vulnerable Code ```markdown ## 安装 ```bash pip install super-productivity-cli ``` ``` ### Technical Analysis The skill directs users or agents to install `super-productivity-cli` directly from the default Python Package Index without specifying an exact version, validating cryptographic hashes, using a lock file, or documenting verified package provenance. Consequently, the installed artifact and its transitive dependencies may change after the skill has been reviewed. The package implementation is not included in this project, so the behavior executed during package installation and subsequent invocation of the `sp` command cannot be verified through this audit. If the package publisher account, distribution infrastructure, or a transitive dependency is compromised, a malicious release could be delivered through the documented installation command. Source distributions may execute package-controlled build logic during installation, while malicious wheel or dependency code could execute when the installed CLI is invoked. ### Attack Path 1. An attacker compromises the package publisher, package repository distribution path, or one of the package's unconstrained transitive dependencies. 2. The attacker publishes a malicious release under the expected package name. 3. A user or agent follows `SKILL.md` and runs `pip install super-productivity-cli`. 4. Because no version or hash is specified, pip resolves and downloads the currently available package and dependencies. 5. Attacker-controlled code executes during an applicable source build or when the user subsequently invokes the installed `sp` command. 6. The malicious code operates with the privileges of the account running pip or the CLI. ### Impact Assessment Successful exploitation ...[truncated 522 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to an exact, reviewed version rather than installing the latest available release: ```bash pip install super-productivity-cli==<reviewed-version> ``` 2. Generate and maintain a dependency lock file that pins all transitive dependencies. 3. Require cryptographic hashes during installation, such as by using a hash-locked requirements file with `pip install --require-hashes`. 4. Document the package's verified official repository, publisher identity, expected package index, and release provenance. 5. Review package source and dependency changes before updating the pinned version. 6. Install the package in an isolated virtual environment under a non-administrative account. 7. Prefer reproducible, signed, or internally mirrored artifacts where operationally possible.