T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned Remote Dependency Is Downloaded and Executed During Validation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 50
Vulnerability Type: Unpinned third-party tool execution
Risk Level: MediumVulnerable Code Snippet:
markdown - For workflow edits, run `actionlint` if available or via `go run github.com/rhysd/actionlint/cmd/actionlint@latest <files>`.Technical Analysis
The validation instructions use
go runwith the mutable@latestversion selector. This causes Go tooling to retrieve source code from an external dependency source and execute whichever release is considered latest at invocation time.Because the executed code is not pinned to an audited version or immutable commit, its effective contents can change after this skill has been reviewed. If the upstream repository, module distribution path, maintainer account, or a related supply-chain component is compromised, malicious code could be delivered through a future version and executed automatically during workflow validation.
This is classified as
T08: Insecure Dependenciesbecause the principal weakness is execution of an unpinned third-party dependency from an unsafe mutable source.Attack Path
- An attacker compromises the upstream
actionlintrepository, a maintainer account, or another relevant part of the Go module distribution chain. - The attacker publishes or causes a malicious release to be selected by the
@latestversion query. - A user invokes this skill for edits involving workflow files.
- The agent follows the validation instruction and executes:
shell go run github.com/rhysd/actionlint/cmd/actionlint@latest <files> - Go downloads, compiles, and executes the attacker-controlled module code.
- The malicious code runs with the permissions and environmental access of the agent process.
Impact Assessment
Successful exploitation could execute arbitrary code under the account running the agent. Depending on the execution environment and sandbox restrictions, this ...[truncated 620 chars]
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Pin
actionlintto a reviewed, immutable version rather than using@latest, for example:shell go run github.com/rhysd/actionlint/cmd/actionlint@vX.Y.Z <files> - Review the selected release and commit before adopting it. Update the pinned version only through an explicit dependency-review process.
- Prefer a trusted, preinstalled
actionlintbinary when available, and verify its expected version before execution. - Use Go module checksum verification and retain the expected dependency checksums in controlled project metadata where applicable.
- In sensitive environments, prohibit automatic network dependency retrieval during validation. Install the approved tool in a controlled build image or retrieve it through a trusted internal artifact registry.
- Run validation tools with least privilege, restricted filesystem access, no unnecessary credentials, and limited network connectivity.
- Pin
