T08 · Insecure Dependencies
Warning
- Location
scripts/generate_image.py:3- Finding
Unpinned OpenAI SDK Dependency Creates a Supply-Chain Risk
- Content
View full analysis
=3.7" # dependencies = [ # "openai", # ] # /// ``` The installation documentation similarly requests the latest available package without a version or integrity constraint: ```text - Need Install python openai sdk: pip instsall openai ``` ### Technical Analysis The project declares the `openai` package without pinning a reviewed version or verifying package integrity. Consequently, the code executed by the skill depends on whichever compatible package release the package resolver selects at installation or execution time. If the upstream package, package index, dependency resolution path, or a transitive dependency is compromised, malicious code could run when the package is installed or imported. The documented installation command also contains the typo `instsall`, which is a reliability problem and could encourage users to seek untrusted alternative installation instructions. No malicious dependency is currently proven to be present. The vulnerability is the absence of controls ensuring that future installations resolve to a known, reviewed artifact. ### Attack Path 1. An attacker compromises a future `openai` package release, a transitive dependency, or the dependency distribution channel. 2. A user installs the dependency according to `SKILL.md`, or a script runner automatically resolves the inline dependency declaration. 3. Because no exact version or package hash is required, the resolver downloads the attacker-controlled artifact. 4. Malicious package code executes during installation or when `from openai import OpenAI` is imported. 5. The code runs with the same filesystem, environment, network, and credential access as the user or Agent invoking the skill. ### Impact Assessment Successful explo ...[truncated 385 chars]- Remediation
View remediation
", # ] ``` 2. Maintain a lockfile containing hashes for the direct dependency and its transitive dependencies. 3. Install packages only from a trusted, explicitly configured package index. 4. Incorporate dependency vulnerability and integrity scanning into release checks. 5. Review and deliberately update the pinned version instead of accepting updates automatically. 6. Correct the documentation to use a valid, pinned command, such as: ```bash python -m pip install "openai==" ``` 7. Prefer installation inside an isolated virtual environment with only the permissions required by the skill. ]]>