Consul CLI

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:31 PM UTC
• Version:
  1.0.0

Overview

This is a Consul CLI reference with powerful administrative examples, but it does not install or run hidden code.

Install only if you want an agent to reference Consul administration commands. Before running mutating commands, confirm the cluster, datacenter, namespace, token, and target nodes; back up KV/snapshots first; keep root tokens and SecretIDs out of chat logs and shell history; and require explicit approval for recursive deletes, snapshot restores, force-leave, Raft changes, service deregistration, consul exec, watch handlers, locks, and writes under `/etc`.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Behavioral AST: exec() Call, eval() Call, Dynamic Import
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (9)

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The guide includes state-changing and potentially destructive Consul operations such as service deregistration, ACL modification, snapshot restore, force-leave, and Raft peer removal without clear warnings about operational impact, recovery implications, or production safeguards. In a command-reference skill, this can lead an agent or user to execute high-impact cluster actions without confirming environment, backups, or authorization.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The ACL bootstrap and token management sections show creation, reading, and assignment of highly sensitive credentials, including the root token, without strong handling guidance. This is dangerous because these commands can expose secrets in terminal history, logs, screenshots, shell process listings, or agent outputs, enabling privilege escalation and full Consul compromise.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The skill provides remote command execution examples via `consul exec` and automated command triggers via `consul watch` without explicit warnings that these can run commands across multiple nodes. In an agent skill, this materially increases risk because a model may treat them as routine operational examples and cause unintended fleet-wide command execution or service disruption.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The `consul kv delete` examples demonstrate destructive operations, including recursive deletion, without any warning that they permanently remove KV entries and may affect dependent services. In an operational CLI reference, users may copy-paste examples directly, so omission of guardrails increases risk of accidental data loss.

Missing User Warnings

High

• Confidence: 97% confidence
• Finding: `consul snapshot restore` can overwrite or roll back cluster state, affecting services, KV data, ACLs, and coordination state. Documenting restore without a strong warning may lead operators to execute a highly disruptive operation on the wrong environment or without validating backup provenance and downtime implications.

Missing User Warnings

High

• Confidence: 96% confidence
• Finding: The examples show remote execution of arbitrary shell commands across nodes without warning about scope, privilege, and blast radius. Because users may copy these commands directly, this creates a meaningful risk of accidental fleet-wide disruption or unintended command execution in production.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The watch examples execute shell handlers in response to cluster events or state changes, which can repeatedly trigger commands and create unintended automation loops or local command execution risks. Without warnings, users may not appreciate that these are active execution hooks rather than passive monitoring examples.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: `consul force-leave` forcibly removes nodes from cluster membership and can affect cluster stability, service discovery, and recovery workflows. Omitting a warning increases the chance of operators using it as a routine action rather than a targeted remediation step.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The configuration sync script writes directly to `/etc/app/config.env` based on KV contents without warning about overwriting system configuration, formatting issues, or the trust boundary of KV data. This can lead to accidental config corruption, privilege-sensitive file modification, or unsafe propagation of unvalidated values.

VirusTotal

63/63 vendors flagged this skill as clean.