Back to skill

Security audit

Pve Automation

Security checks for vulnerabilities and agentic risk

Overview

This Proxmox automation skill is not malicious, but it needs Review because it handles privileged infrastructure credentials with unsafe TLS defaults and documents broad destructive admin operations.

Install only if you are comfortable letting an agent assist with privileged Proxmox administration. Use a least-privilege non-root API token, avoid passing secrets on the command line, enable proper TLS certificate verification before real use, and require explicit human confirmation for deletes, rollbacks, storage/IAM changes, upgrades, and other disruptive actions.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/pve_client.py:55
Finding

TLS Certificate Verification Is Disabled for Authenticated API Requests

Content
View full analysis
= 400: ``` The Skill documentation also recommends commands that disable certificate validation: ```bash # 1. Get ticket and CSRF token curl -k -d 'username=root@pam' --data-urlencode 'password=secret' \ https://pve.example.com:8006/api2/json/access/ticket # Response: { "data": { "ticket": "...", "CSRFPreventionToken": "..." } } # 2. Use ticket in subsequent requests curl -k -b "PVEAuthCookie=" \ -H "CSRFPreventionToken: " \ https://pve.example.com:8006/api2/json/nodes ``` ### Technical Analysis The client uses HTTPS but explicitly passes `verify=False` to every request. This prevents `requests` from validating whether the server certificate is trusted and whether it belongs to the requested host. Suppression of `InsecureRequestWarning` further conceals this unsafe state from operators. Every request includes the PVE API token in the `Authorization` header: ```python self.headers = { 'Authorization': f'PVEAPIToken={self.user}!{self.token_id}={self.token_secret}' } ``` Consequently, an attacker who can intercept or redirect network traffic can present an arbitrary TLS certificate. The client will accept the certificate and send its authentication token to the attacker-controlled endpoint. The documented `curl -k` ticket-authentication workflow creates the same exposure for usernames, ...[truncated 2028 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/pve_client.py:234
Finding

API Token Secret Can Be Exposed Through Command-Line Arguments

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (30)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The skill claims broad Proxmox automation coverage, but the concrete implementation/examples only partially cover that scope while the documentation expands into many sensitive admin actions. This mismatch increases the chance of over-trust by an agent or operator, who may authorize the skill for broad infrastructure control based on an inaccurate description.

Content

No source excerpt is available for this finding.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
86% confidence
Finding

The example uses a root-scoped API token in a header, normalizing direct use of highly privileged credentials for automation. If copied into real deployments, this encourages excessive privilege and increases the impact of token leakage or misuse to full cluster compromise.

Content

Scanner excerpt · SKILL.md (reported line 64)May include surrounding context.

Authorization: PVEAPIToken=USER@REALM!TOKENID=UUID

Example

curl -H 'Authorization: PVEAPIToken=root@pam!automation=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee'
https://pve.example.com:8006/api2/json/nodes

text

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
94% confidence
Finding

The documented DELETE VM endpoint is inherently destructive and can cause irreversible service interruption and data loss if triggered without strong safeguards. In an agent skill, exposing deletion primitives without mandatory confirmation and authorization checks makes accidental or unauthorized destruction more likely.

Content

Scanner excerpt · SKILL.md (reported line 128)May include surrounding context.

POST /nodes/{node}/qemu/{vmid}/status/reset

Delete VM

DELETE /nodes/{node}/qemu/{vmid}

text

### LXC Container Operations

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
94% confidence
Finding

The container deletion endpoint can irreversibly remove workloads and data. Given this skill's automation framing, inclusion of direct deletion commands without prominent safeguards increases the risk of accidental or unauthorized destructive actions.

Content

Scanner excerpt · SKILL.md (reported line 147)May include surrounding context.

POST /nodes/{node}/lxc/{vmid}/status/stop

Delete container

DELETE /nodes/{node}/lxc/{vmid}

text

### VM/Container Creation

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
91% confidence
Finding

Snapshot deletion removes recovery points and can hinder incident recovery or rollback after failed changes. In automation, exposing this operation without clear warnings and confirmation can silently reduce resilience and increase outage impact.

Content

Scanner excerpt · SKILL.md (reported line 247)May include surrounding context.

md
POST /nodes/{node}/qemu/{vmid}/snapshot/{snapname}/rollback

# Delete snapshot
DELETE /nodes/{node}/qemu/{vmid}/snapshot/{snapname}

# Create backup
POST /nodes/{node}/vzdump

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
89% confidence
Finding

Deleting HA groups can remove failover constraints and protection policies for production workloads, increasing availability risk across the cluster. In this context, that is a sensitive operational control that should not be casually exposed in a general VM automation skill.

Content

Scanner excerpt · SKILL.md (reported line 826)May include surrounding context.

  • nofailback: 1 = stay on current node after recovery

Delete HA group

DELETE /cluster/ha/groups/{group}

text

**HA Resources (VMs to protect):**

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
90% confidence
Finding

Removing HA-managed resources disables automated recovery for protected VMs/containers. This can directly reduce resilience and lead to prolonged downtime during node failures, making it a high-impact administrative action.

Content

Scanner excerpt · SKILL.md (reported line 844)May include surrounding context.

  • max_relocate: Max relocate attempts (default: 1)

Remove from HA

DELETE /cluster/ha/resources/{sid}

text

**HA Status and Control:**

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
93% confidence
Finding

Deleting backup artifacts is destructive and can permanently remove the ability to restore systems after compromise, corruption, or operator error. In infrastructure automation, exposing backup deletion without strict controls materially increases recovery risk.

Content

Scanner excerpt · SKILL.md (reported line 981)May include surrounding context.

GET /nodes/{node}/storage/{storage}/content/{backup-file}

Delete backup

DELETE /nodes/{node}/storage/{storage}/content/{backup-file}

text

### 5. Scheduled Jobs

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
86% confidence
Finding

Deleting scheduled jobs can silently disable backups or other recurring operational tasks, causing latent security and reliability issues. The danger is amplified because the impact may not be noticed until a recovery or maintenance event fails.

Content

Scanner excerpt · SKILL.md (reported line 1010)May include surrounding context.

md
PUT /cluster/jobs/{id}

# Delete job
DELETE /cluster/jobs/{id}

# Get job execution log
GET /cluster/jobs/{id}/log

Context-Inappropriate Capability

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

User, group, role, ACL, and pool administration are identity and authorization controls, not routine VM/container automation. If used improperly, these capabilities can create privileged accounts, alter access control, or remove protections across the cluster, leading to full administrative compromise.

Content

No source excerpt is available for this finding.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
97% confidence
Finding

Deleting users is an identity-management action with broad security implications, including denial of access, disruption of automation, and tampering with audit/accountability structures. In a skill not scoped to IAM administration, this materially expands abuse potential and blast radius.

Content

Scanner excerpt · SKILL.md (reported line 1043)May include surrounding context.

PUT /access/users/{userid}

Delete user

DELETE /access/users/{userid}

text

**Groups:**

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
95% confidence
Finding

Deleting groups can implicitly alter access for multiple users and services at once, causing privilege changes or outages. Because group membership is often foundational to authorization design, this is a sensitive administrative action outside the core VM-management use case.

Content

Scanner excerpt · SKILL.md (reported line 1058)May include surrounding context.

  • comment: Description

Delete group

DELETE /access/groups/{groupid}

text

**Roles:**

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
97% confidence
Finding

Deleting ACLs can abruptly remove or alter access controls on clusters, pools, or VMs, potentially locking out operators or disabling security boundaries. Since ACLs govern authorization, exposing direct removal in a broad automation skill creates severe misuse potential.

Content

Scanner excerpt · SKILL.md (reported line 1100)May include surrounding context.

path: "/pool/production", groups: "developers", roles: "PVEVMUser"

Remove ACL

DELETE /access/acl?path={path}&users={userid}&roles={role}

text

**Pools:**

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
87% confidence
Finding

Pool deletion can disrupt organizational grouping, delegated access models, and automation that depends on pool membership. While not always directly destructive to VM data, it can create operational confusion and authorization side effects.

Content

Scanner excerpt · SKILL.md (reported line 1121)May include surrounding context.

  • members: Array of objects with type and id

Delete pool

DELETE /pools/{poolid}

text

### 7. Notifications (Webhooks)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
85% confidence
Finding

Deleting replication jobs can silently remove disaster-recovery protections, increasing exposure to node or storage failures. This is a sensitive reliability control that should be explicitly treated as high-trust in automation.

Content

Scanner excerpt · SKILL.md (reported line 1190)May include surrounding context.

POST /nodes/{node}/replication/{id}/run_now

Delete replication job

DELETE /nodes/{node}/replication/{id}

text

### 9. Firewall

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
96% confidence
Finding

Deleting storage configuration can sever access to disks, backups, templates, or images and may cascade into outages or data inaccessibility across many workloads. In a general-purpose automation skill, this is one of the highest-blast-radius operations documented.

Content

Scanner excerpt · SKILL.md (reported line 1301)May include surrounding context.

md
PUT /storage/{storage}

# Delete storage
DELETE /storage/{storage}

# Get storage status
GET /nodes/{node}/storage/{storage}/status

Context-Inappropriate Capability

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

Certificate management, host subscription handling, apt update/upgrade, and node diagnostics are host-administration capabilities outside the stated scope. These actions can affect trust boundaries, service availability, and host integrity, especially when upgrades or proxy restarts are triggered remotely.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown file lists operations such as stop, reset, delete, rollback, and create actions, plus examples for creating and starting VMs, but does not warn that these actions can interrupt services, remove resources, or revert state. Under the markdown-specific warning criterion, behavior that can affect user data or system integrity should be accompanied by clear cautions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

The file instructs users to set PVE_SECRET and also shows passing --token-secret directly on the command line, but it does not warn that secrets in shell history, process listings, or shared terminals may be exposed. Because this markdown describes behavior affecting privacy and credentials, a warning is expected.

Content

No source excerpt is available for this finding.

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
99% confidence
Finding

The README explicitly states the implementation uses verify=False, which disables TLS certificate verification and permits man-in-the-middle interception of API traffic. In a Proxmox automation skill handling privileged infrastructure operations and API credentials, this materially increases the risk of credential theft, command tampering, and unauthorized VM or cluster actions.

Content

Scanner excerpt · README.md (reported line 181)May include surrounding context.

md
## Production Notes

- Current implementation uses `verify=False` (SSL verification disabled), suitable only for trusted internal environments
- For production, use valid certificates and enable SSL verification
- Apply least-privilege principles to API tokens; avoid over-privileged root tokens

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding

The skill documents network/API usage and includes code that can read environment-derived configuration, but the manifest does not declare any tool scope or permissions. This creates a governance gap where an agent may invoke network-capable behavior without explicit review, making unintended external access and misuse harder to constrain.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The activation text uses broad trigger phrases like generic VM management and virtualization automation, which can cause the skill to be selected for loosely related requests. Because the skill also documents highly privileged and destructive PVE operations, over-broad activation increases the chance of inappropriate invocation in sensitive contexts.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill advertises destructive capabilities such as delete, rollback, and storage/user removal without upfront safety warnings in the main description. In infrastructure automation, omission of prominent destructive-operation warnings increases the risk of accidental data loss, outage, or irreversible administrative changes.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 64)May include surrounding context.

Authorization: PVEAPIToken=USER@REALM!TOKENID=UUID

Example

curl -H 'Authorization: PVEAPIToken=root@pam!automation=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee'
https://pve.example.com:8006/api2/json/nodes

text

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
99% confidence
Finding

The example Python client disables TLS certificate verification with verify=False and suppresses related warnings. This permits man-in-the-middle interception of API traffic, exposing highly privileged Proxmox credentials and enabling command tampering against infrastructure-management requests.

Content

Scanner excerpt · SKILL.md (reported line 771)May include surrounding context.

md
response = requests.request(
            method, url,
            headers=self.headers,
            verify=False,
            **kwargs
        )
        response.raise_for_status()