T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:89
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 89–93 **Vulnerability Type**: Supply-chain risk from an unpinned third-party dependency **Risk Level**: Medium ```markdown ## MCP Server ```bash pip install mcp-seedance ``` ``` ### Technical Analysis The skill instructs users to install `mcp-seedance` from the configured Python package index without specifying a reviewed version or cryptographic hashes. The package is external to this project, and its implementation was not included in the audited artifact. Python package installation may execute package-controlled build or installation logic. Because the dependency is unpinned, a later compromised or malicious release could be installed even if an earlier version had been reviewed. The instruction also does not require source provenance verification, hash validation, an isolated virtual environment, or a restricted installation account. This is classified as **T08: Insecure Dependencies**. The audit found no evidence that the package is currently malicious; the vulnerability is the unsafe, mutable dependency-installation process. ### Attack Path 1. An attacker compromises the package publisher account, package repository, release pipeline, or another relevant supply-chain component. 2. The attacker publishes a malicious release under the expected `mcp-seedance` package name. 3. A user follows the documented `pip install mcp-seedance` instruction. 4. Pip resolves the unpinned dependency to the attacker-controlled release. 5. Malicious build or package code executes during installation or when the installed MCP integration is subsequently invoked. 6. The code operates with the privileges of the user running pip and may access resources available to that account. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on the local environment, this may expose files, API cre ...[truncated 447 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to a specifically reviewed version, for example `mcp-seedance==X.Y.Z`. 2. Verify package provenance and provide a link to the authoritative source repository and publisher identity. 3. Use a lock file or requirements file containing cryptographic hashes, and install with `pip --require-hashes`. 4. Review the pinned package, its build configuration, and all transitive dependencies before recommending installation. 5. Recommend installation inside a dedicated virtual environment or disposable container under a non-privileged account. 6. Avoid exposing `ACEDATACLOUD_API_TOKEN` during package installation and grant the token only to the runtime process that requires it. 7. Prefer the documented direct HTTPS API workflow when MCP functionality is unnecessary. 8. Establish a controlled upgrade process so newer package versions are reviewed and hash-pinned before adoption.