T08 · Insecure Dependencies
- Location
install.sh:24- Finding
Unpinned MCP Dependency Is Downloaded and Executed at Runtime
- Content
View full analysis
Vulnerability Details
File Location:
install.sh:24-28,40;SKILL.md:33-36;README.md:24,39-43;mcp.example.json:5-6
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: HighVulnerable Code
install.sh:24-28:bash # @rebind.gg/mcp-server ships via npm; bunx fetches it on demand. # --no-probe: the default probe spawns the server and fails if the relay isn't # running yet; the selftest below is the real verifier. if openclaw mcp add rebind --no-probe \ --command bunx --arg @rebind.gg/mcp-server \install.sh:40:bash bunx @rebind.gg/mcp-server --selftest || die "Rebind relay not reachable on ws://127.0.0.1:19561.SKILL.md:33-36:sh openclaw mcp add rebind --no-probe \ --command bunx --arg @rebind.gg/mcp-server \ --env REBIND_URL=ws://127.0.0.1:19561 openclaw config set skills.entries.rebind-computer-use.env.REBIND_URL ws://127.0.0.1:19561README.md:39-43:sh openclaw skills install @usinput/rebind-computer-use openclaw mcp add rebind --no-probe \ --command bunx --arg @rebind.gg/mcp-server \ --env REBIND_URL=ws://127.0.0.1:19561 openclaw config set skills.entries.rebind-computer-use.env.REBIND_URL ws://127.0.0.1:19561mcp.example.json:5-6:json "command": "bunx", "args": ["@rebind.gg/mcp-server"],Technical Analysis
The installation instructions and configuration execute
@rebind.gg/mcp-serverthroughbunxwithout specifying an exact package version or verifying an integrity digest. Package resolution can therefore select a release different from the one reviewed during this audit.The installer also invokes the package directly during its self-test. Registration causes the same remotely resolved package to be executed again whenever OpenClaw starts the MCP server. Trust is consequently delegated to the package registry, package publisher account, DNS and TLS infrastructure, and every future package release.
There is no evidence in the reviewed ...[truncated 1426 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace every unversioned package reference with an exact, audited version, for example:
bash bunx @rebind.gg/mcp-server@X.Y.Z -
Apply the same exact version in
install.sh,SKILL.md,README.md, andmcp.example.jsonso that installation and runtime behavior remain consistent. -
Prefer installing the dependency from a lockfile rather than resolving it dynamically during every launch.
-
Verify the package archive against a trusted cryptographic digest before execution.
-
Consider vendoring a reviewed release or distributing a signed executable through a controlled release channel.
-
Disable automatic version drift. Upgrade only through an explicit process that includes source review, integrity validation, and security testing.
-
Use package provenance or signature verification where supported, and restrict package publication to accounts protected by strong multifactor authentication.
-
Execute the MCP server inside a sandbox with only the filesystem, network, and process permissions required for its documented operation.
-
