T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Mandatory Unpinned Alibaba Cloud CLI Plugin Installation and Updates
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 34-43
Vulnerability Type: Mutable, unpinned dependency installation
Risk Level: MediumComplete Code Snippet:
markdown - [MUST] Run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. - [MUST] Run `aliyun plugin update` to ensure installed plugins are always current. ... > aliyun configure ai-mode enable > aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-ehpc-instant-job-skill" > aliyun plugin updateTechnical Analysis
The Skill mandates enabling automatic plugin installation and running an unconditional plugin update. No plugin version is pinned, and the workflow does not independently verify a package signature, digest, or allowlisted artifact before installation.
Consequently, the locally executed plugin code may differ from the code present when the Skill was audited. This creates a mutable supply-chain execution path. Because the Alibaba Cloud CLI operates in a context that may have access to environment-based credentials,
~/.aliyun/config.json, or ECS RAM-role credentials, a compromised plugin or update channel could execute with the Agent user's local permissions and the configured cloud identity.The behavior is not required on every invocation to perform the declared job-management operations. Verifying that a compatible, audited plugin is already installed would be sufficient in normal operation.
Attack Path
- The Skill is loaded and follows its mandatory initialization instructions.
- It enables automatic CLI plugin installation.
- It invokes
aliyun plugin updatewithout pinning an audited version. - A compromised upstream artifact, repository, distribution channel, or plugin release supplies malicious plugin code.
- The Alibaba Cloud CLI installs or executes that mutable code locally.
- The plugin inherits the process's ...[truncated 775 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the requirement to enable automatic plugin installation on every run.
- Pin the required plugin to a specific, reviewed version.
- Verify the downloaded artifact using a publisher signature or a trusted, pinned cryptographic digest.
- Use an explicit allowlist for plugin names, versions, and distribution endpoints.
- Check for an already installed compatible plugin before attempting installation.
- Treat installation and updates as separate administrative operations requiring explicit user confirmation.
- Run plugin installation in a restricted environment without production credentials.
- Document a tested rollback procedure and retain the last known-good plugin artifact.
