T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/huawei_cloud/dispatcher.py:1469- Finding
Read-only migration Skill exposes destructive cloud operations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill presents itself as read-only migration planning, but its packaged dispatcher can run live cloud and Kubernetes changes and can expose sensitive cluster data.
Install only after reviewing and removing or isolating the mutation actions, and run it with a least-privilege read-only Huawei IAM user and read-only Kubernetes RBAC. Do not use production credentials with write permissions, do not request Secret data, and prefer pinned dependencies with normal TLS verification enabled.
scripts/huawei_cloud/dispatcher.py:1469Read-only migration Skill exposes destructive cloud operations
scripts/huawei_cloud/network.py:765TLS certificate verification disabled for signed NAT inventory requests
scripts/huawei_cloud/storage.py:400TLS certificate verification disabled for signed SFS inventory requests
SKILL.md:67Unpinned third-party dependencies installed at runtime
The skill is described as a read-only migration planning tool, but the file implements numerous state-changing operations including cluster deletion, node deletion, workload scaling/resizing/deletion, hibernation, EIP binding, and node cordon/drain actions. This capability mismatch is dangerous because an orchestrator or user may invoke the skill under the assumption that it is inventory-only, enabling destructive actions that can disrupt or destroy production environments.
The skill enumerates Kubernetes Secrets and can optionally return secret data contents, which is not justified for migration planning and directly exposes credentials, tokens, keys, and other sensitive application material. This turns a planning/inventory skill into a credential-access mechanism and can enable lateral movement, data theft, and cluster or application compromise.
configure_cce_hpa performs live cluster mutation by creating or replacing HorizontalPodAutoscaler resources, directly contradicting the skill's stated read-only migration-planning purpose. In a delegated agent environment this is a serious trust-boundary violation, because a caller selecting a planning skill could unknowingly trigger production autoscaling changes that affect availability, cost, and workload behavior.
The skill description promises read-only inventory and planning, but this code can execute remote state-changing operations such as immediate repair, manual repair, ignore, not_ignore, verify, and whitelist changes against HSS-managed vulnerabilities. This violates the user's expected safety boundary and can directly alter host security state or trigger remediation on production systems.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: container-migration-planner
description: Use this skill for Huawei Cloud CCE migration planning, resource inventory, delivery方案, dependency mapping, and migration risk assessment without executing changes.
---
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Direct IAM authentication, ECS lookup by node IP, and per-node security-group inspection are more invasive and lower-level than a migration planner should imply. This expands credential handling and cloud-account visibility beyond the stated task, increasing both confidentiality and abuse risk.
Detected: suspicious.exposed_secret_literal, suspicious.insecure_tls_verification