T08 · Insecure Dependencies
- Location
SKILL.md:226- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 226
Vulnerability Type: Unpinned and mutable third-party dependency
Risk Level: MediumVulnerable Code Snippet:
markdown | dashscope | Python SDK | Required | pip install dashscope |Technical Analysis
The installation instruction uses
pip install dashscopewithout specifying a reviewed version or an integrity hash. Consequently, the installed artifact depends on the package version currently resolved by pip and on the configured package index.This does not establish that the named dependency is malicious. However, it creates a supply-chain exposure because future releases are not covered by the original Skill review. A compromised package release, package repository, dependency account, or local pip index configuration could cause an unexpected artifact to be installed. Transitive dependencies are also left unlocked and unverified.
Attack Path
- An attacker compromises a package release, an upstream dependency, a configured package index, or the dependency publication process.
- The attacker publishes a malicious or otherwise compromised version that satisfies the unrestricted installation command.
- A user follows the Skill documentation and executes
pip install dashscope. - Pip resolves and installs the compromised version because no version constraint or integrity hash is enforced.
- Malicious code may execute during installation or when the package is subsequently imported by the video-analysis workflow.
Impact Assessment
Successful exploitation could execute attacker-controlled code with the privileges of the user running pip or the analysis process. Depending on those privileges and the environment, the attacker could access user-readable files, application credentials such as the configured DashScope API key, video inputs, network resources, and writable project or user directories.
The issue does not indep ...[truncated 171 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
dashscopeto a specifically reviewed version rather than installing an unrestricted latest release. - Place direct and transitive dependencies in a lock file generated from a trusted environment.
- Require package integrity hashes, such as with a hash-locked requirements file and
pip install --require-hashes. - Configure pip to use an explicitly trusted package index and prevent unintended fallback to untrusted or privately configured repositories.
- Review dependency updates before changing the pinned version, including release provenance, dependency changes, and known vulnerabilities.
- Install and run the dependency in an isolated virtual environment or container under a non-privileged account.
- Restrict the runtime environment so it can access only the required videos, configuration fields, and network endpoints.
- Document a reproducible installation command, for example:
bash python -m pip install --require-hashes -r requirements.txt- Pin