ClawHub
Back to skill

Security audit

Olares Settings (olares-cli settings)

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation-only helper for using Olares settings commands, and its sensitive actions are disclosed and tied to that purpose.

Install only if you intend to let an agent help manage an Olares instance. Review commands before approving writes, especially user deletion, app env/domain changes, VPN ACL or SSH changes, integration credential reads, and backup password rotation. Keep access keys, SSO tokens, generated passwords, backup passwords, and TLS private keys out of chat transcripts and shell history.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill advertises destructive operations (`users create/delete`) and secret-handling actions (`integration accounts add`, SSO-related surfaces) directly in the top-level description without an upfront warning that some commands can change state, expose one-time credentials, or require careful secret input handling. This increases the chance an agent invokes risky verbs too casually based only on trigger text, especially because the description encourages broad use when users mention settings-related topics.

Missing User Warnings

Medium
Confidence
85% confidence
Finding
The documentation instructs users to provide a TLS certificate and private key file for third-party domain configuration, and notes that the PEM bytes are POSTed verbatim, but it does not prominently warn that this is highly sensitive key material that must not be exposed in logs, chat, transcripts, or shell history. In an agent-assisted CLI context, omission of that warning increases the chance the agent or user handles private keys unsafely, causing credential compromise for the domain.

Static analysis

No suspicious patterns detected.