T08 · Insecure Dependencies
- Location
references/cli-installation-guide.md:27- Finding
Unpinned Executable Downloads and Automatic Plugin Updates
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for Alibaba Cloud PAI/SysOM diagnosis, but it asks users to make persistent CLI and cloud-authorization changes that are broader and less clearly controlled than a read-only diagnosis tool should require.
Review before installing. Use a narrowly scoped RAM policy instead of full-access managed policies, avoid global auto-plugin-install where possible, verify any Aliyun CLI download through trusted package/signature mechanisms, and run commands only after validating region/resource IDs and understanding that the workflow may change local CLI configuration and Alibaba Cloud authorization state.
references/cli-installation-guide.md:27Unpinned Executable Downloads and Automatic Plugin Updates
references/diagnose-workflow.md:219Shell and JSON Injection Exposure in User-Controlled CLI Parameters
references/ram-policies.md:55Managed-Policy Guidance Exceeds the Skill's Documented Minimum Permissions
The description says the skill should be used for 'Any issue related to EAS instance health, DLC job health, or underlying compute resource performance,' which is a broad catch-all rather than a narrowly bounded trigger. This can overlap with many unrelated or non-SysOM issues and may cause unintended invocation because no negative examples or tighter constraints are given for that clause.
The file requires ocd_description to be 'in English' and later repeats that it must contain 'no Chinese characters, no spaces,' which imposes a language constraint on user input. This is a natural-language policy concern because the skill forces a specific language rather than offering translation help, opt-in, or a documented locale-specific justification.
The skill claims to perform read-only diagnosis, but its workflow changes local CLI state by enabling AI mode, setting a user agent, enabling auto-plugin installation, and updating plugins. These persistent changes alter the operator environment beyond the stated scope and can create unintended side effects, trust-boundary violations, or future command behavior changes on the host.
The documentation says the operations are read-only and that no cleanup is needed, yet the workflow itself requires disabling AI mode afterward and earlier makes other persistent CLI changes. This mismatch can leave modified local settings in place if execution is interrupted, causing follow-on commands to behave differently or exposing the environment to unnecessary plugin or telemetry behavior.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# macOS amd64
curl -O https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-amd64.tgz
tar xzf aliyun-cli-macosx-latest-amd64.tgz
sudo mv aliyun /usr/local/bin/
# Linux amd64
curl -O https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
curl -O https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz tar xzf aliyun-cli-linux-latest-amd64.tgz sudo mv aliyun /usr/local/bin/
### Windows
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**4b. Product Auto-Inference**
The `product` field is determined automatically from the `instance` prefix — do NOT ask the user to confirm unless inference fails:
| Instance Prefix | Inferred Product |
|----------------|-----------------|
The instruction requires ocd_description to be in English only, with no Chinese characters, which is a language-policy constraint expressed in natural language. The document does not offer the user a language choice or explain a justified locale limitation, so it fits the policy-violation category.
The document defines successful completion as disabling AI-Mode at the end, but it does not warn that this modifies the user's persistent CLI configuration state. Silent state-changing cleanup steps can surprise users, break later workflows, or disable features they intentionally enabled, which is a real security and safety concern even if the direct impact is limited.