ClawHub
Back to skill

Security audit

huawei-cloud-ascend-profiler-db-explorer

Security checks for vulnerabilities and agentic risk

Overview

The skill needs review because its troubleshooting instructions can expose private profiling data to other local users.

Before use, remove the chmod 644 troubleshooting step and preserve private database permissions. Use a read-only database connection and a trusted query executor. The documented query_profiler_db.py command cannot run from this package because the script is missing; any replacement needs separate review.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Code capability 'file_read' detected in scripts/get_schema.py but not covered by declared permissions.

High
Category
MCP Least Privilege
Confidence
75% confidence
Finding

The skill uses 'file_read' capability that is not covered by the declared 'allowed-tools' preapproval. Review the host runtime's actual enforcement policy; runtime permissions are unknown unless separately verified, and this declaration alone does not establish a permission ceiling.

Content

No source excerpt is available for this finding.

The troubleshooting instructions make the profiling database readable by all local users without warning about the privacy impact.

Medium
Category
Output Handling
Confidence
97% confidence
Finding

The troubleshooting command chmod 644 profiling.db grants read permission to every local user, potentially exposing profiling metadata that was previously private. Exploitation requires access through the containing directories, but this blanket permission change is unnecessary for database analysis and is particularly risky on shared systems.

Content

No source excerpt is available for this finding.