T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party Tool Execution and Unverified Package Installation
- Content
View full analysis
[--source ssc|github|net] # install ado-package from ssc, net or github ``` ``` ### Technical Analysis The documented `uvx stata-mcp` invocation does not pin `stata-mcp` to an exact, reviewed version or require artifact integrity verification. Depending on the local `uvx` cache and environment, following this instruction may retrieve and execute the currently published package rather than the version assessed when the Skill was reviewed. The Skill also permits Stata ado packages to be installed from SSC, GitHub, or a generic `net` source. It does not require an approved repository, an immutable Git commit, a checksum, a signature, or explicit user authorization. GitHub branches and generic network sources are mutable, so their content can change after review. This creates a supply-chain trust gap: the effective code executed by the workflow is controlled partly by external package publishers and remote repositories rather than by the reviewed Skill package. ### Attack Path 1. An attacker compromises the `stata-mcp` distribution channel or a maintainer account, publishes a malicious update, or introduces a deceptive dependency. 2. Alternatively, an attacker controls or compromises a GitHub or `net` source selected for ado installation. 3. An agent follows the Skill instructions and runs the unpinned `uvx stata-mcp` command or installs the remote ado package. 4. The package manager retrieves the mutable, unverified artifact. 5. The retrieved tool or ado package e ...[truncated 1171 chars]- Remediation
View remediation
