T08 · Insecure Dependencies
- Location
SKILL.md:6- Finding
Unpinned External Runtime and Dependency Retrieval
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:6,SKILL.md:56-62,INSTALL.md:7-22,scripts/build.sh:9-18, andscripts/build.ps1:8-19
Vulnerability Type: Supply-chain risk caused by mutable external sources and unverifiable runtime components
Risk Level: MediumComplete Code Snippets
SKILL.md:6:text metadata: {"openclaw":{"emoji":"📁","homepage":"https://github.com/go-fs-mcp/go-fs-mcp","requires":{"bins":["go-fs-mcp-skill","go-fs-mcp-server"],"config":["skill.json"]},"install":[{"kind":"go","package":"github.com/go-fs-mcp/go-fs-mcp-server/cmd/server@latest","bins":["go-fs-mcp-server"]},{"kind":"go","package":"github.com/go-fs-mcp/go-fs-mcp-skill/cmd/skill@latest","bins":["go-fs-mcp-skill"]}]}}SKILL.md:56-62:bash From the go-fs-mcp source repository, build both binaries and place them in this Skill directory or add them to PATH: git clone https://github.com/go-fs-mcp/go-fs-mcp.git cd go-fs-mcp go build -o go-fs-mcp-server/go-fs-mcp-server ./go-fs-mcp-server/cmd/server go build -o go-fs-mcp-skill/go-fs-mcp-skill ./go-fs-mcp-skill/cmd/skillINSTALL.md:7-22:bash git clone https://github.com/go-fs-mcp/go-fs-mcp.git cd go-fs-mcp export GOPROXY=https://goproxy.cn,direct go mod tidy go build -o go-fs-mcp-server/go-fs-mcp-server ./go-fs-mcp-server/cmd/server go build -o go-fs-mcp-skill/go-fs-mcp-skill ./go-fs-mcp-skill/cmd/skill chmod +x go-fs-mcp-server/go-fs-mcp-server go-fs-mcp-skill/go-fs-mcp-skillscripts/build.sh:9-18:bash export GOPROXY="${GOPROXY:-https://goproxy.cn,direct}" echo "==> go mod tidy" go mod tidy echo "==> build go-fs-mcp-server" go build -o go-fs-mcp-server/go-fs-mcp-server ./go-fs-mcp-server/cmd/server echo "==> build go-fs-mcp-skill" go build -o go-fs-mcp-skill/go-fs-mcp-skill ./go-fs-mcp-skill/cmd/skillscripts/build.ps1:8-19:powershell if (-not $env:GOPROXY) { $env:GOPROXY = "https://goproxy.cn,direct" } Write-Host "==> go mod tidy" go mod tidy Write ...[truncated 2841 chars]- Remediation
View remediation
Remediation Suggestions
- Replace every
@latestpackage reference with an immutable, reviewed version or commit. - Update clone instructions to check out a specific commit hash after cloning, and document the expected hash.
- Include the auditable runtime source,
go.mod, andgo.sumin the reviewed distribution or link the package to an immutable source archive. - Build with dependency-lock integrity enforced, and avoid running
go mod tidyas part of routine installation. - Prefer an explicitly trusted dependency source. If a proxy is required, document its trust assumptions and provide a controlled fallback policy.
- Publish signed release artifacts and provide cryptographic checksums from an independently authenticated channel.
- Make installation scripts verify artifact signatures or checksums before making binaries executable or installing them into the Skill directory.
- Generate and publish an SBOM for both binaries, and scan direct and transitive Go dependencies before release.
- Run the server with least privilege and restrict its filesystem access to explicitly approved roots so a compromised dependency cannot access the entire user-visible filesystem.
- Require security review and reproducible-build verification before updating any pinned source or dependency version.
- Replace every
