T08 · Insecure Dependencies
- Location
references/INSTALL.md:7- Finding
Unpinned External Repository and Dependency Execution
- Content
View full analysis
Vulnerability Details
File Location:
references/INSTALL.md:7-18,references/INSTALL.md:24-29,references/TROUBLESHOOTING.md:5-9,references/OPENCLAW_MCP_CONFIG.json:4-7, andreferences/OPENHANDS_MCP_CONFIG.json:3-6
Vulnerability Type: Supply-chain risk caused by installing and executing mutable external code
Risk Level: MediumVulnerable Code
references/INSTALL.md:7-18:markdown 1. Clone the public repository: ```bash git clone https://github.com/xiaojiou176-open/shopflow-suite.git cd shopflow-suite pnpm install- Start the read-only MCP surface:
bash pnpm mcp:stdiotext `references/INSTALL.md:24-29`: ```markdown 4. Verify the packet surface: ```bash pnpm verify:catalog pnpm verify:release-readinesstext `references/TROUBLESHOOTING.md:5-9`: ```markdown ## 1. MCP will not start - run `pnpm install` - run `pnpm mcp:stdio` - confirm the command is being run from the real Shopflow repo rootreferences/OPENCLAW_MCP_CONFIG.json:4-7:json "shopflow": { "command": "pnpm", "args": ["mcp:stdio"], "cwd": "/absolute/path/to/shopflow-suite" }references/OPENHANDS_MCP_CONFIG.json:3-6:json "shopflow": { "command": "pnpm", "args": ["mcp:stdio"], "cwd": "/absolute/path/to/shopflow-suite" }Technical Analysis
The installation procedure clones the default branch of an external GitHub repository without pinning a reviewed release tag or immutable commit hash. It then invokes
pnpm install, which may execute dependency lifecycle scripts, followed by several scripts whose implementations are controlled by the downloaded repository.The two MCP configurations also cause the host to execute the repository-defined
mcp:stdioscript whenever the Shopflow MCP server is launched. Consequently, the code that is ultimately installed and executed can change after this Skill package has ...[truncated 1801 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the external repository to a reviewed, immutable commit hash rather than cloning and running its default branch directly.
- Publish versioned releases and require verification through signed Git tags, release signatures, or documented cryptographic checksums.
- Require a committed pnpm lockfile and use
pnpm install --frozen-lockfileso dependency resolution cannot silently change. - Audit all package lifecycle scripts. Where compatible, initially install with
pnpm install --ignore-scriptsand explicitly run only reviewed build steps. - Document the expected contents or cryptographic hash of the
mcp:stdio,verify:catalog, andverify:release-readinessscript implementations. - Enumerate and verify the exact MCP tools exposed by the reviewed server version before connecting it to an agent host.
- Run installation and the MCP server in a sandbox or container with minimal filesystem access, no unnecessary secrets, restricted network access, and a dedicated unprivileged account.
- Prefer distributing the reviewed server implementation with the Skill or referencing a reproducible, immutable release artifact.
