T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Third-Party SDK Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23–25
Vulnerability Type: Unpinned third-party dependency
Risk Level: Mediummarkdown ## SDK 安装与基础调用 ```bash pip install google-genai # 官方 SDKtext ### Technical Analysis The documented installation command retrieves the latest available `google-genai` package and its transitive dependencies from the package index configured for `pip`. It provides no exact version constraint, lockfile, or cryptographic hash verification. Although the package is represented as Google's official SDK and the document does not specify a suspicious package source, the dependency remains mutable after this Skill's review. A future compromised, malicious, or unexpectedly incompatible release could introduce unsafe installation-time or runtime behavior. The risk also depends on whether the user's package-index configuration and network path are trustworthy. ### Attack Path 1. A user follows the installation instructions. 2. `pip` resolves the latest `google-genai` release and its transitive dependencies from the configured index. 3. A package maintainer account, distribution channel, configured mirror, or dependency release is compromised or begins serving malicious content. 4. Because no reviewed version or integrity hash is enforced, `pip` accepts the changed package. 5. Malicious package code executes during installation, import, or subsequent SDK use with the privileges of the invoking user or environment. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the privileges of the user running `pip` or importing the package. Depending on that environment, the attacker could access application data and credentials available to the process, modify files writable by the user, make network requests, or compromise the associated virtual environment. The project itself does not request elevated privileges, so system-wide impact wo ...[truncated 78 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
google-genaito an exact, reviewed version rather than implicitly installing the latest release. - Record all transitive dependencies in a lockfile generated from a trusted environment.
- Require cryptographic hashes during installation, for example:
bash python -m pip install --require-hashes -r requirements.txt - Install dependencies in a dedicated, least-privileged virtual environment or container.
- Use only trusted package indexes and explicitly configure approved index URLs where appropriate.
- Enable dependency vulnerability and provenance monitoring, then review and deliberately update pinned versions.
- Avoid running package installation as
rootor another privileged account.
- Pin
