T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Automatic Installation of Unpinned Alibaba Cloud CLI Plugins
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:47-64
Vulnerability Type: Unpinned executable dependency installation
Risk Level: MediumVulnerable Code
bash aliyun configure set --auto-plugin-install true aliyun plugin list aliyun rds --help aliyun configure listThe Skill additionally directs the Agent to install plugins by mutable short name:
bash aliyun plugin install --names <product>The same automatic plugin configuration also appears in
references/verification-method.md:44.Technical Analysis
The Skill enables Alibaba Cloud CLI's automatic plugin installation and permits plugins to be installed using only a product short name. It does not require a pinned plugin version, integrity checksum, trusted publisher verification, or validation of the retrieved executable artifact. It also does not direct the Agent to restore the previous global auto-install setting after completing the task.
Alibaba Cloud CLI plugins are executable dependencies. Their behavior can change independently of the reviewed Skill package. Consequently, the code ultimately executed by the Skill is not fully represented by the audited files. This creates a supply-chain boundary where a compromised plugin repository, publishing account, or mutable plugin release could introduce unreviewed local code.
Attack Path
- The Agent executes
aliyun configure set --auto-plugin-install true. - A required product plugin is absent or an API request causes plugin resolution.
- Alibaba Cloud CLI retrieves a plugin selected by its mutable product name.
- If the distribution channel or plugin release is compromised, the malicious plugin is installed.
- The plugin executes with the same operating-system privileges and cloud credentials available to the Agent.
- Because auto-install remains globally enabled, later CLI operations may continue retrieving executable components without an explici ...[truncated 527 chars]
- The Agent executes
- Remediation
View remediation
Remediation Suggestions
- Do not enable automatic plugin installation globally as a default readiness step.
- Require explicit user or tool approval before installing executable dependencies.
- Pin each plugin to a tested version when the CLI supports version selection.
- Verify the plugin's trusted publisher, signature, and cryptographic checksum before execution.
- Record and restore the previous
auto-plugin-installsetting after the task. - Prefer verified, preinstalled plugins in controlled environments.
- Revalidate the exact plugin version and action help before each cloud operation.
- Document the trusted plugin source and reject unexpected mirrors or repositories.
