Huawei Cloud Cce Cluster Management

• Outcome: Review
• Latest audit: Jun 16, 2026 · 8:20 PM UTC
• Version: 0.1.1

Overview

This appears to be a legitimate Huawei CCE administration skill, but it needs review because it can change live cloud infrastructure and expose kubeconfig credentials with incomplete safeguards.

Install only if you intend to let an agent administer Huawei Cloud CCE resources. Use least-privilege Huawei credentials, avoid production accounts at first, treat kubeconfig output and node passwords as secrets, and require explicit human approval before create, delete, resize, drain, addon, or EIP operations.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (14)

Intent-Code Divergence

Medium

• Confidence: 92% confidence
• Finding: The document states that all dangerous operations require `confirm=true`, but later marks some state-changing operations such as create, bind EIP, unbind EIP, and update actions as not requiring confirmation. This inconsistency can cause operators or downstream agents to trust a blanket safety guarantee that does not actually hold, increasing the risk of unintended infrastructure changes.

Intent-Code Divergence

Medium

• Confidence: 84% confidence
• Finding: The skill claims sensitive authentication material is never persisted, yet it explicitly supports retrieving cluster kubeconfig, which commonly contains reusable cluster credentials or tokens. Even if the skill itself does not write files, exposing kubeconfig in outputs creates a clear path for credential disclosure, copy/paste persistence, logging leakage, or reuse by unauthorized parties.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger list is broad enough to activate on generic Kubernetes or cloud-administration requests such as 'create cluster', 'delete cluster', or 'addon' without clear Huawei CCE intent. That can cause the agent to invoke a powerful infrastructure-management skill in the wrong context, increasing the chance of unintended destructive actions or disclosure of sensitive cluster access material.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The kubeconfig retrieval tool explicitly returns cluster access material that can grant administrative access to the Kubernetes API, yet the manifest provides no warning about its sensitivity, storage, sharing, or least-privilege implications. In a cluster-management skill, this is especially dangerous because the feature is operationally legitimate but directly exposes credentials that could enable full cluster compromise if mishandled.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: Binding a public EIP to the cluster API server increases external exposure of a highly sensitive management endpoint, but the manifest does not warn the user about the security implications. In this skill context, making control-plane access public is a legitimate admin action, yet without clear caution it can lead to accidental internet exposure and increased attack surface.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The node drain operation evicts workloads and can disrupt live services, but the tool description does not clearly warn about service impact or possible downtime. Because this skill is intended for production cluster operations, the omission raises the chance of an operator triggering disruptive maintenance without understanding the operational consequences.

Missing User Warnings

Medium

• Confidence: 86% confidence
• Finding: The document provides copyable examples for creating clusters, nodes, node pools, and installing addons without any warning that these actions provision billable cloud resources and can change production infrastructure. In an agent skill context, omission of impact/cost warnings increases the chance of unintended destructive or expensive operations being executed from routine prompts.

Missing User Warnings

Medium

• Confidence: 81% confidence
• Finding: The guide tells users to export a node password into an environment variable without any caution about shell history, process exposure, CI logging, or secret management. While environment variables are commonly used, presenting this pattern without safety guidance can lead to credential leakage in shared terminals, automation pipelines, or debugging output.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The documentation explicitly recommends and enumerates destructive IAM permissions such as cluster creation, deletion, and update operations without clearly warning that these actions can disrupt workloads, expose services, or permanently destroy infrastructure. In a cluster-management skill, operators may copy the policy as-is and overgrant privileges, increasing the blast radius if the skill is misused, misconfigured, or invoked with compromised credentials.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The documentation instructs users to place a node login password in the CCE_NODE_PASSWORD environment variable and emphasizes automatic processing, but it does not warn that environment variables can be exposed through shell history, process inspection, CI logs, crash dumps, or inherited child processes. In a cluster-management skill, these credentials can grant direct node access, so omission of handling warnings materially increases the chance of credential leakage.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The documentation instructs users to place a node password in a plaintext environment variable (`export CCE_NODE_PASSWORD="your_password"`) without any warning about shell history, process/environment exposure, CI log leakage, or safer alternatives. In a cluster-management skill, these credentials are especially sensitive because they can grant node-level access and may be reused or harvested from automation environments.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The troubleshooting guide instructs users to export a plaintext node password into an environment variable without warning about shell history, process environment leakage, CI/CD logs, or multi-user host exposure. In a cloud cluster management skill, these credentials are sensitive because they can grant node access and may be copied into automation contexts where environment variables are widely exposed.

Credential Access

High

• Category: Privilege Escalation

Content

|------|----------|------------|
| `huawei_list_cce_clusters` | List all CCE clusters in region | `region` |
| `huawei_get_cce_nodes` | Get detailed node information | `region`, `cluster_id`, `node_id` |
| `huawei_get_cce_kubeconfig` | Get cluster kubeconfig | `region`, `cluster_id`, `duration` |

### Cluster Management

• Confidence: 89% confidence
• Finding: kubeconfig

Credential Access

High

• Category: Privilege Escalation

Content

|------|----------|------------|
| `huawei_list_cce_clusters` | List all CCE clusters in region | `region` |
| `huawei_get_cce_nodes` | Get detailed node information | `region`, `cluster_id`, `node_id` |
| `huawei_get_cce_kubeconfig` | Get cluster kubeconfig | `region`, `cluster_id`, `duration` |

### Cluster Management

• Confidence: 89% confidence
• Finding: kubeconfig

VirusTotal

63/63 vendors flagged this skill as clean.

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical

• Code: suspicious.exposed_secret_literal
• Location: references/cce-cluster-parameters.md:163