T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/huawei_cloud/dispatcher.py:1470- Finding
Alarm-focused skill exposes broad destructive cloud and Kubernetes operations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This alarm-correlation skill packages a much broader Huawei Cloud and Kubernetes admin interface than it discloses, including secret-reading and infrastructure-changing actions.
Install only in a tightly restricted test environment or after the publisher removes the undeclared dispatcher actions and secret-return paths. Do not use broad production Huawei Cloud or Kubernetes credentials with this package; if it must be evaluated, use a dedicated least-privilege identity limited to the documented AOM actions and assume command output or logs could expose sensitive cluster data.
scripts/huawei_cloud/dispatcher.py:1470Alarm-focused skill exposes broad destructive cloud and Kubernetes operations
scripts/huawei_cloud/cce.py:3313Dispatcher permits extraction of raw Kubernetes Secret values across all namespaces
scripts/huawei_cloud/cce.py:3375Kubernetes API TLS verification is disabled while client credentials are written to predictable temporary files
The skill can enumerate Kubernetes Secrets and optionally return raw secret data, which may include credentials, tokens, keys, and connection material. This is unrelated to alarm correlation and creates a direct secret-exfiltration path from production clusters through the skill interface.
The skill can list Kubernetes Secrets and, when include_data is enabled, return secret material directly to the caller. In the context of an alarm-correlation skill, this is highly dangerous and unjustified because it enables credential and token extraction from the cluster, facilitating privilege escalation, lateral movement, and compromise of dependent systems.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: alarm-correlation-engine
description: 华为云 AOM 告警关联分析技能,支持查询 active/history 告警、当前活跃告警、告警去重归并、严重级别分组、突发/常态告警识别,以及告警规则查询、创建、修改、删除、动作规则和静默规则核对。
---
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Querying ECS-by-IP and VPC security group data appears aimed at security posture or connectivity inspection rather than AOM alarm analysis. The mismatch is relevant because it introduces additional infrastructure discovery capabilities under a misleading label.
Detected: suspicious.exposed_secret_literal, suspicious.insecure_tls_verification