T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned External MCP Source Is Built and Executed
- Content
View full analysis
&2 echo "Build on Windows:" >&2 echo " cd ${NOTE_SYNC_REPO}/mcp-server && go build -o note-sync-mcp.exe" >&2 exit 1 fi exec "${EXE}" ``` ### Technical Analysis The installation instructions clone the current default branch of an external repository and build it without pinning an audited commit, immutable release, checksum, or cryptographic signature. The launcher subsequently executes the generated binary as the configured MCP server. The external MCP implementation is not included in the audited project. Consequently, this audit cannot verify that the binary only appends notes, correctly confines writes to the intended notes directory, safely sanitizes titles, avoids network access, or protects inherited environment data. The repository URL also uses the placeholder owner `your-org`, preventing identification of a concrete, trusted upstream source. This creates a supply-chain trust gap: the code reviewed during Skill publication is not necessarily the code users later retrieve and execute. ### Attack Path 1. An attacker compromises the external repository, gains control of its default branch, or causes users to resolve the placeholder URL to an unsafe source. 2. The attacker modifies the MCP source to include arbitrary b ...[truncated 1075 chars]- Remediation
View remediation
