Back to skill

Security audit

vmware-vdi

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marks this skill suspicious because a scanner confirmed guidance to disable TLS verification, which could expose VDI credentials to interception; scan coverage is incomplete.

Consider the credential-interception risk before installing. The scan was partial: two local references were unresolved, so the evidence is incomplete and does not establish that the skill is safe.

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
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/cli-reference.md (reported line 8)May include surrounding context.

Setup & diagnostics

bash
vmware-vdi init [--force] [--skip-test]     # friendly setup: prompt, write config + .env, test, discover pools
vmware-vdi doctor                           # config / credentials / connectivity checks
vmware-vdi mcp                              # run the MCP server (stdio) — the primary MCP entry point

The troubleshooting instructions recommend disabling TLS verification without warning about credential interception.

Medium
Category
Output Handling
Confidence
97% confidence
Finding

The troubleshooting guidance recommends disabling certificate verification, allowing an attacker positioned on the network to impersonate the Connection Server and intercept Horizon credentials or authentication tokens. Restricting the advice to self-signed labs reduces exposure but does not authenticate the server; the privileged account and disruptive VDI operations make a successful interception particularly consequential.

Content

No source excerpt is available for this finding.