ClawHub
Back to skill

Security audit

Kubernetes Storage

Security checks for vulnerabilities and agentic risk

Overview

This Kubernetes storage helper needs review because its creation example also deletes storage without clearly separating or authorizing that destructive step.

Before use, require explicit approval for deletion of the exact cluster, namespace, and claim. Keep deletion separate from provisioning, check the bound volume's reclaim policy and consuming workloads, and verify recoverable backups for valuable data. Restrict the integration's permissions to the intended resources.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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)

The PVC deletion example lacks a warning about potential permanent data loss.

High
Category
Output Handling
Confidence
96% confidence
Finding

The PVC example includes an executable deletion call without distinguishing it as a destructive operation or requiring confirmation. If an agent treats the example as a sequential workflow against an existing claim, deletion can disrupt workloads and, where the bound PV uses the Delete reclaim policy, permanently remove backing storage; the StorageClass example explicitly uses that policy.

Content

No source excerpt is available for this finding.

Activation keywords include broad everyday terms without requiring Kubernetes context.

Medium
Category
Trigger Abuse
Confidence
98% confidence
Finding

The skill activates on mentions of terms such as "data", "disk", "volume", and "persist", which occur in many unrelated requests. Although the description identifies Kubernetes storage as the domain, these explicit activation rules do not require that context or provide exclusions.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.